stream-handbook

Here are some interactive tutorials on using Node where you work to make various tests pass: http://nodeschool.io/ This is also good: https://github.com/substack/stream-handbook

Sorry, I would like to know that too but I only stumbled over this gem myself while reading the well written node.js stream handbook: https://github.com/substack/stream-handbook Edit: the "dmr" part in the URL seems to point to this being an anecdote by the late Dennis Ritchie :( http://cm.bell-labs.com/who/dmr/index.html

Appears to be heavily inspired by Node.js Streams[1]. Would love this pattern to be copied to other languages aswell. [1] https://github.com/substack/stream-handbook

I like the separation of the transports into engine.io, however it would be even better if it exposed a standard Node.js Stream interface so that it played nicely with the growing ecosystem of Stream-related modules. Dominic Tarr, substack, and others have been advocating this idea for awhile: https://github.com/substack/stream-handbook Gluing together various types of streams and stream transformers is a really nice way to build certain types of applications. Fortunately it should be easy to write a Stream compatible wrapper.

Node.js has another beautiful way of doing this. It's called streams there. https://github.com/substack/stream-handbook http://nodejs.org/api/stream.html

Because technologies like Q [1] and streams [2] provide a very abstractions around doing long-running tasks asynchronously, which jives better with node's entire philosophy. Combine that with the fact that running multiple processes is a perfectly viable way to do actual long-running tasks and node provides abstractions around that out of the box, and it really starts to look like fibers and webworkers in node are patchy hold-overs for technologists who haven't fully changed into thinking about things in "the node way." [1] https://github.com/kriskowal/q [2] https://github.com/substack/stream-handbook

This is a really cool and ambitious project. Although some mention ShareJS, I would say that the OT portion more closely resembles that employed by Firebase in their Firepad project [1] (in that no centralized server manages ordering and history). Actually, this system has many of the features of Firebase in a self-hosted package. As a user of ShareJS (for the real-time collaboration on Plunker [2]), I can see some interesting benefits offered by TogetherJS; the system has cursor and presence features out of the box. That being said, the main drawback that I see in TogetherJS is that it seems to be tightly coupled in a way that it is hard to take smaller parts of the overall system. It would be great if the P2P network system could be extracted and plugged into a node.js Stream interface. That would allow the code to plug into a whole ec