Why singleton? about vonage-node-sdk HOT 5 CLOSED

Technically it doesn't have to be a singleton. I will plan on changing this in a future release. In the mean time below is the workaround for you to try.

var nexmo = require('EASYNEXMO');
var enexmo = require('easynexmo');
var dnexmo = require('EASYnexmo');
nexmo.initialize("key1","secret1",true);
enexmo.initialize("key2","secret2",true);
dnexmo.initialize("key3","secret3",true);

I dont personally like this but something to get you going while I get this change done.

from vonage-node-sdk.

@pvela any help required?

from vonage-node-sdk.

@pvela @wertlex - I've experimented in a branch that does a few things:

1. Moves to ES2015 and uses Babel transpilation
2. Moves towards a non-singleton API, but still uses the singleton within the Nexmo instance for now
3. Makes a start towards having functions live on related namespaces as per Must be namespaced by concept in the WiP (work in progress) library spec https://github.com/Nexmo/client-library-specification/blob/master/SPECIFICATION.md#api-methods

Any thoughts on this? e.g.

• Are we okay moving to ES2015?
• Do we think taking an incremental approach to non singltons is a good approach? Will it avoid a big bang and thus big changes?

Edit: Here's the branch https://github.com/Nexmo/nexmo-node/tree/namespaces

from vonage-node-sdk.

I am ok to move to ES2015. Thats the future 👍 .
I started doing a big bang approach in the old repo, but didn't make much progress. Having thought about it and made some initial design I can say for sure that its a good idea to take an incremental approach.

from vonage-node-sdk.

We are moving away from the singleton approach. Closing this question as answered.

from vonage-node-sdk.