Creating two clients re-uses variables from the first client

[topfunky]

I'm sending a video out to two different clouds using the Node.js client.

When I create a second client, I get an error that the API request wasn't properly signed. It appears that the Panda client is caching variables internally, which makes it impossible to use it twice in an app.

The script works fine if I use either the configuration data from cloudA or from cloudB.

var clientA, clientB, options, panda;

panda = require('panda');

options = {
  source_url:  'http://example.com/my-video.mov',
  payload:     'my-video',
  path_format: 'my-video/:id'
};

clientA = panda.createClient(config['cloudA']);
clientA.post('/videos.json', options, function(response) {
  return console.log(response);
});

// This throws an error about the wrong URL and args. Works fine alone.
clientB = panda.createClient(config['cloudB']);
clientB.post('/videos.json', options, function(response) {
  return console.log(response);
});

[zimbatm]

/cc @vivienschilis

[vivienschilis]

Hi @topfunky, we were not 'Watching' this repo strangely.
We fixed the issue on master I think.

Can you have give it a try?

[vivienschilis]

Oh ok no I think I found the issue.

[vivienschilis]

Actually,

I did this test:
https://gist.github.com/vivienschilis/6000075
I and I get two different results.

What's your nodejs version?

[vivienschilis]

Ok can actually, can you use git master and tell me if that works. thx

[vivienschilis]

Ok I updated npm with the latest version

[topfunky]

Thanks, Vivien! I'll try it out.

On Mon, Jul 15, 2013 at 7:17 AM, Vivien Schilis [email protected]:

Ok I updated npm with the latest version

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-20972225
.

Geoffrey Grosenbach
[email protected]
........................
PeepCode Screencasts
http://peepcode.com