dnode

You may be interested in dnode[0] as well. Protocol documented here[1]. [0] https://github.com/substack/dnode [1] https://github.com/substack/dnode-protocol/blob/master/doc/p...

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.

Just in case this saves someone's time: phantomjs-node uses ridiculous hacks. Not being rude but I think the author was drunk when writing that. I ended up wasting quite some time when trying to customize it. You do NOT need to use any hacks whatsoever to run dnode on phantom, just browserify(https://github.com/substack/node-browserify) the shoe and dnode modules and use the example code at https://github.com/substack/dnode .

Yes, DNode (https://github.com/substack/dnode) will actually do most of this stuff and it is a pluggable library. For Joint, we wanted to make a really clean interface just for single page apps where you're only focusing on function calls rather than HTTP headers, cookies, routes, etc. A lot of the small 1-off apps we were making and thinking of making just had a couple HTTP requests for static files then a bunch of AJAX or socket.io calls. We think that in this case, the limitations imposed by Joint will help inspire creative solutions.

Check out tap, it has a very simple api that works well for testing asynchronous code: https://github.com/isaacs/node-tap Here's a tap example that sets up a server and client for dnode: https://github.com/substack/dnode/blob/master/test/single.js Timers usually aren't necessary with test harnesses like tap or nodeunit since you need to call `t.end()` explicitly or else `t.plan()` the number of tests that are supposed to be run. If a different number of tests actually run or assertions fire after `t.end()` is called, those are reported as errors. For (4), to run a bunch of test files in a directory you can use the `tap` command. You can even add something like `tap test/*.js` to the scripts.test field of a package.json file and then to run all your tests you can just do `npm test`.

Here are some of Mojito's existing Node.JS counterparts: * https://github.com/substack/dnode * https://github.com/tblobaum/nodeQuery * https://github.com/socketstream/socketstream

Fun fact, hook.io uses Dnode as it's primary TCP transport, which is written by Substack! http://github.com/SubStack/dnode

VNC + node-rfb + node-binary + node-png + dnode + browserify http://github.com/pkrumins/node-rfb http://github.com/substack/node-binary http://github.com/pkrumins/node-png http://github.com/substack/dnode http://github.com/substack/node-browserify

> It looks like it is claiming to support lots of internode cluster-type communication There are a few projects that specifically take advantage of node's ability to proxy and distribute work across multiple processes. Check out these projects: http://learnboost.github.com/cluster/ https://github.com/nodejitsu/node-http-proxy https://github.com/substack/dnode Or my very early prototype botnet thingie: https://github.com/isaacs/sodn

have a look at dnode: https://github.com/substack/dnode bidirectional remote method invocation. Oh, and a complimentary robot free of charge: http://substack.net/browse/2010-11-08%2022:16:39 :-)

Somewhat unrelated, but anyone interested in NowJS should definitely check out https://github.com/substack/dnode first...

I wanted to cross post this here as I already posted it in the comments. ----- I am glad you wrote about this, but I feel you are missing the real 'magic' that can be done with node.js and Backbone, or any client code you choose. Socket.io is great, fantastic even, and I think it is something that really shows the power of node.js; there is something built on top of socket.io that is even more wonderful, and it is called dnode[0]. It is really simple to use, but has a lot of potential for server process to server process and server to client communication. It is in effect RPC, and I really can't do it justice. For the example you give up here, you could easily overwrite the Backbone.sync function and have it instead send the appropriate objects you need to fetch models on the server, while having the server call back to the client with sa

There's also an interesting concept in the NodeJS community called dnode. There's no python lib for it yet though (ruby and perl exist). https://github.com/substack/dnode

I know this. They use dnode (https://github.com/substack/dnode) for most of their inter-process/inter-browser communication, which uses socket.io for the web action.