29 Aug, 2011, Runter wrote in the 1st comment:
Votes: 0
I'm launching a web service called Parley that will be free to all beta testers forever. If you're interested in beta testing contact me and I'll set you up with an account. More information follows.

The service is a clone of what http://pusher.com/ offers with some extras. The main difference is the price points and the extent of the service. Parley is going to be free for non-industrial use. Pusher caps connections and messages rather low. I plan on having unlimited messages. Parley aims to deliver real time interaction to web sites and web content fast and painlessly. It uses a REST Api. Your app posts to Parley and Parley sends the message on to a specific socket(s) that you have chosen in your post. Parley offers 1 to many relationships and is very fast. It's perhaps faster than sending down the message individually yourself. Furthermore, with Parley you can use cloud services that traditionally don't support many technologies Parley brings to the table. Such as web sockets, and a variety of fallback options.

Unlike pusher, Parley supports *all browsers*. Even ones that require the most ancient techniques for real time interactions. Redis handles about 150,000 operations a second. Parley is built on node.js & socket.io using Redis to atomically queue messages received for consumer shards to send out through web sockets. And not just websockets.
The fallback lists is as follows:

* Native Web Sockets
* Adobe Flash Socket
* AJAX long polling
* AJAX multipart streaming
* Forever Iframe
* JSONP Polling

One of the great things about using a service like this is you decouple yourself from the router stack your app uses. Different cloud based services support different things. It's somewhat a headache trying to build these solutions around their architecture. I know, because I've been doing it. It's terrible.

I'm working out some kinks atm, but the website can be found here: http://parleyme.herokuapp.com/. Right now it just shows how many messages have been sent. The API is built, but I'm modifying it enough that it wouldn't be useful to document it here. I'll follow up with more information soon for those who may be interested in using the service. But the basic process is you server the javascript to your user that uses the Parley socket code to connect to Parley using your application key you got from Parley. You also include an arbitrary channel they're subscribed to. It can be unique, or none unique. It can be a list of channels. Then you just write the code on how to react to the events the messages they receive. All of the technological hurdles of getting the message to the client is taken care of.
29 Aug, 2011, Runter wrote in the 2nd comment:
Votes: 0
P.s. the Parley site itself uses Parley to update the number of messages that have been sent using Parley.
30 Aug, 2011, Idealiad wrote in the 3rd comment:
Votes: 0
So maybe a simple question, but would it be worth it to write a mud with a service like this for sending messages to your connections? You'd still have to manage the connections yourself, right?
30 Aug, 2011, Runter wrote in the 4th comment:
Votes: 0
You wouldn't have to manage the connections, but no mud clients support any of the web technologies that Parley uses. It would be possible to write a stand alone client, but probably not worth the time when compared to just writing a web client. (html, flash, or java applet, etc)