now

I used to use a project called now on npm that was abandoned a few years ago (https://github.com/Flotype/now). I was curious how this new project was using the same name on npm as the previous now that I had used. Looking at the npm release history, versions <= 0.8.1 are the old project, and the new project picked up at 0.9.0 (should have been 1.0.0 I guess). This is consistent with npm's statements about package name transfers during the leftpad debacle, but there's just something weird about reusing package names for totally different projects...

Does this support sticky sessions? Normally I think it's best for HTTP backends to be stateless, but WebSockets open up interesting possibilities for RPC solutions like NowJS (https://github.com/Flotype/now), dnode (https://github.com/substack/dnode), and others (https://github.com/kriskowal/q-connection) that benefit from keeping state in memory in the app servers. I'd be interested to hear about other load balancing techniques for WebSockets.

Now.js has been abandoned by its authors [0], and bitrot is creeping in. Someone stepped in to maintain it, but has barely touched it ever since [1]. 0. https://github.com/Flotype/now/issues/208 1. https://github.com/jameskeane/now/commits/master/

This is the company of nowjs https://github.com/flotype/now. Many of the technical details should be available at github or in the code to find out more without providing an email

I wonder how it compares with Flotype's[1] Now: https://github.com/Flotype/now [1] YC W2011