While webhooks have a particular role at the exclusion of others (for example, they are silly to think of being used to do realtime to the browser or desktop client), they do work in tandem with socket-like persistent connections, mostly useful for getting to the desktop, or getting through firewalls, etc. Also, with really high throughput it makes a lot of sense to do something like the Twitter Stream API instead of webhooks.
That said, people keep looking to webhooks to solve "realtime to the browser" or things like this. This shows there is obviously a need for it. While it's possible to do with a lot of tools (Orbited, fancy/hacky Comet setups, etc), I've been working on just solving this issue. In essence, "the Real Time Web as a Service." (Although as a Platform is maybe more apt)
I was doing it on my own time, but I was recently hired at very webhook-centric company to build this as a cloud service. And we're in a private preview now. If you'd like to try this out, please email me directly.
--
Jeff Lindsay
http://progrium.com
--
You received this message because you are subscribed to the Google Groups "WebHooks" group.
To post to this group, send email to
webh...@googlegroups.com.
To unsubscribe from this group, send email to
webhooks+u...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/webhooks?hl=en.