messageHasSubscribers returns true when subscriptions have been canceled about pubsubjs HOT 1 CLOSED

I've been thinking about this one, and been trying to understand the discussion in issue 11 as well.

It seems to me that you're trying to add tight(er) coupling / control in a place where it doesn't belong. Publish/subscribe is all about passing messages about topics, giving up control (and coupling) and trusting the system to respond appropriately.

The if statement is a dead giveaway ... it's a control statement :)

Perhaps what you need for your application is "Flow-based programming": http://en.wikipedia.org/wiki/Flow-based_programming

You could for instance use http://noflojs.org

In my understanding, that would give you a few key benefits:

• loose coupling of components
• the originator of a message still doesn't have to worry about branching code, just passing the message
• priority / fallback mechanism, that if DO_SOMETHING fails for a message/topic DO_SOMETHING_ELSE will give it a go as well

Basically, in a flow-based system, control would be at the receiver and not of the publisher of messages.

I wouldn't be at all surprised that you would be able to implement an elegant flow system using a publish/subscribe library as the transport mechanism.

from pubsubjs.