This only works up to a point. I evaluated http://pusher.com for Poll Everywhere, but decided against it because I didn't want a "tax man" between me and my customers.
I'd argue that most of the folks that use Pusher don't do so in a way that's mission critical to their application (there are a few exceptions). If they did, they would scale up to a certain point where they'd want to get off of Pusher and on to a self-hosted push server.
That's precisely where Pusher fell off the horse for me, so our company created an open source streaming service, http://firehose.io/.
That said, would anybody be interested in a hosted version of Firehose? The "end-game" of a hosted service would always be to run the open source version of this service on your very own servers, and stop paying the middleman tax.
I'd argue that most of the folks that use Pusher don't do so in a way that's mission critical to their application (there are a few exceptions). If they did, they would scale up to a certain point where they'd want to get off of Pusher and on to a self-hosted push server.
That's precisely where Pusher fell off the horse for me, so our company created an open source streaming service, http://firehose.io/.
That said, would anybody be interested in a hosted version of Firehose? The "end-game" of a hosted service would always be to run the open source version of this service on your very own servers, and stop paying the middleman tax.