Realtime Websockets in a Javascript internet device

As everyone here is a Javascript nut, and I'm sure looked at Socket.io at some point, I'm really hoping someone can offer me some advice to save me some time learning the hard way :)

I'm in the process of evaluating whether it's better to run one's own Node server(s) with Socket.io, or use one of the well known realtime WebSocket services out there such as Pusher or PubNub that I am assuming will take away all the pain in regards to running the service.

I was really hoping (and will be most grateful) to get some advice from anyone who's possibly been there and done this already.  Any of your thoughts on the following would be hugely appreciated:

• If you've gone the paid route with Pusher or PubNub, why did you do that?  If home grown / Socket.io, why as well?
• Do you think the global presence of PubNub is that important when it comes to latency?
• Do you find Pusher/PubNub price prohibitive?  Based on my initial calculations, a few millions messages a month over SSL for $49 a month with Pusher seems fair, but do you think I'm off the mark perhaps?  I know Socket.IO is free, but it comes with a price tag once you start running the service yourself...
• Were there any particular features of PubNub or Pusher that you found extremely useful that Socket.IO does not have, such as private channels, or presence for example?
• Having done one or the other, any advice in retrospect?  Any difficulties, problems, or wishes?

Appreciate your feedback if you have any.

Thanks,

Matt

--
You received this message because you are subscribed to the Google Groups "JavaScript Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/javascript-information/-/eM8fYFUtDEwJ.
To post to this group, send email to javascript-information@googlegroups.com.
To unsubscribe from this group, send email to javascript-information+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/javascript-information?hl=en.