Similarities to now.js

[Thomas Fritz]

Hi

What are the main differences and main similarities of socketstream and now.js?
When should i choose SocketStream, when should i use Now.js?

Has anyone practical experience with both?

Kind regards

---
Thomas FRITZ
web http://fritzthomas.com
twitter http://twitter.com/thomasf

[Craig M]

I'm not overly familiar with Nowjs, but I was looking at it before I
found SocketStream.

The most important difference is scalability. Nowjs does not have the
plumbing necessary to persist sessions and pub/sub info to a common
store so when a client gets disconnected they can reconnect to any
process and pick up where they left off. You'd have to write that
yourself with Nowjs. It's a core concept in SocketStream.

Nowjs also doesn't deliver all of your templates and client side
scripts on the first page load. This could be a good or bad thing
depending on your project. If you're making a single page app from
scratch, SocketStream helps you do it better (IMO). If you need to
integrate into an existing app or serve other routes (eg, '/blog' or '/
news', Nowjs might be a better choice. At least until someone comes up
with a middleware module for SocketStream that let's us whitelist
certains routes and handle them before they get to SS. I'll need
something like this eventually, but it's low on my priority list. I
imagine someone else will get to it before I do, but if it still
hasn't been done by the time I need it, I'll be writing a module to do
it.