Pubsub.io - a query based message hub. End of the channel tyranny now
1–10 of 13 posts
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#2Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#3Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#4Saw the presentation on nodecamp.eu last month, it's really cool stuff. Great you finally made it available to the public.
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#5How complex would it be to execute a javascript function callback against each published document on the hub instead of a query and return the document to the subscriber if the function returns true?
Plus queries are the power of pubsub.io. Queries can be indexed and compiled on the fly, so hubs scale very well.
If you really need funcions, you can fork the project and I can point you to how to add them.
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#6Saw the presentation on nodecamp.eu last month, it's really cool stuff. Great you finally made it available to the public.
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#7Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#8Edit: or rather: CEP + message queue?
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#9Can someone help me understand -- is this a CEP for js? Edit: or rather: CEP + message queue?
Re: Pubsub.io - a query based message hub. End of the channel tyranny now
#10Can someone help me understand -- is this a CEP for js? Edit: or rather: CEP + message queue?
Its not a message queue, and although its only for js now, it meant to be for everybody. But i dont know what CEP is. Something similar?