How 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?
Not hard at all. We actually had that in early versions but removed it because it's really hard to optimize against functions, and you easily break the hub by injecting long running loops.
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.
[+] [-] benfle|14 years ago|reply
[+] [-] ianjorgensen|14 years ago|reply
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.
[+] [-] checker22|14 years ago|reply
Edit: or rather: CEP + message queue?
[+] [-] ianjorgensen|14 years ago|reply
[+] [-] mirrorskin|14 years ago|reply
[+] [-] ianjorgensen|14 years ago|reply
[+] [-] barighona|14 years ago|reply
[deleted]
[+] [-] bumi|14 years ago|reply