Node.js, redis, and resque (via) Paul Gross has been experimenting with Node.js proxies for allowing web applications to be upgraded without missing any requests. Here he places all incoming HTTP requests in a redis queue, then has his backend Rails servers consume requests from the queue and push the responses back on to a queue for Node to deliver. When the backend application is upgraded, requests remain in the queue and users see a few seconds of delay before their request is handled. It’s not production ready yet (POST requests aren’t handled, for example) but it’s a very interesting approach.
Sign in with 
OpenID
This is basically what Apache does right now, I believe. It has an internal queue of requests, and workers pull from that queue. If a worker goes down (e.g. for restart), then it doesn't pull from that queue. It's not necessarily exposed in an obvious way, but used the right way Apache basically does this.
Ian Bicking - 28th February 2010 23:07 - #