PubSub instanceable about pubsubjs HOT 4 CLOSED

PubSubJS can be compared to a message queue, there is no need to have more than one instance. Having more than one instance will create confusion and will be cumbersome, as you'd have to pass that instance around.

from pubsubjs.

Maybe I didn't get it, but

• How should I deal with many instances of the same class which all publish similarly named events?
• How do I avoid event name conflicts between remote parts in my app?

Why not give every publisher its own PubSub as suggested by @maltmann , instead of a global PubSub singleton?
I'll attempt to fork and make it instantiable, since it seems easy and straight forward.

Thanks for the nice lib anyway!
Semmel

from pubsubjs.

@mroderick - while using a global singleton is clearly simpler and more convenient, having the option for specific instances is a good idea. For example, if there are a couple of apps in the same browser, etc.

so +1 for instantiation.

from pubsubjs.

@KutnerUri if that's your need, then you should be using a library that supports that. event emitter is a good choice.

from pubsubjs.