redis-node-client

If you use git submodules, what you do is exactly like tagging. An example from a project I'm working on: at some point I want to add a submodule for a dependency I need $ git submodule add http://github.com/fictorial/redis-node-client.git deps/redis-node-client this produces a commit with the following diff: diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..1695499 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,3 @@ +[submodule "deps/redis-node-client"] + path = deps/redis-node-client + url = http://github.com/fictorial/redis-node-client.git diff --git a/deps/redis-node-client b/deps/redis-node-client new file mode 160000 index 0000000..5050251 --- /dev/null +++ b/deps/redis-node-client @@ -0,0 +1 @@ +Subproject commit 505025187faf3cf7a211f5e6bfd261e45bd0b1dc Later, whe

Might not be 100% relevant but there's a Node Redis client and Redis can now do publish and subscribe, check out the examples here: http://github.com/fictorial/redis-node-client/tree/master/ex...

Thanks for the shout-out in the slides about the Redis client for Node.js. http://github.com/fictorial/redis-node-client

Nice, good to see more people coming to Node.js. These things are like the modern "Hello, World!". Here's one I hacked up in 10 minutes. It's 40 LOC. http://gist.github.com/366590 The big problem with this is that it's just one server. I'm working on something called "NodeRed" (har har) that lets one scale out the frontend using Redis for communication. It's generic enough to do PUBSUB, chat, games, etc. Here's an overview. http://fictorial.com/NodeRed.png I developed the/a Node.js client for Redis if you care to dive into this stuff: http://github.com/fictorial/redis-node-client

Given how young node.js is it has a lot of modules including: Redis http://github.com/fictorial/redis-node-client memcache: http://github.com/elbart/node-memcache MySQL support using DBSlayer And it's fairly easy to implement other stuff using node.js's TCP module. This said, it could definitely use more modules, but it's a young project and I am sure they will come.

I just jumped on node a few days ago. People who are already comfortable with programming with events and closures in Javascript are going to try Node and say things like "where has this been all my life?". In those few short days Node has highlighted to me just how dramatic of an impact a tool that is close to your language/model of choice can have on your ability to rapidly turn ideas into working code. For a cross section of coders that work with jQuery all day, Node will be a big deal. Node has some really friendly and highly productive people working behind it, chief among them Ryan Dahl ( http://github.com/ry ). To learn Node's ins and outs and have some fun, I spent this weekend building out a simple node-based MapReduce-like work unit processor and needed a lot of random help along the way. When I needed gzip ( http://github.com/w