Re:How NodeJS saved my web application
by transmit101 on Sunday February 28, 2010 @05:46PM
(#1157602)
A queue would be a nice addition before the site goes live (it might be possible to employ a Redis list to do the job).
I'd love to see how far NodeJS could cope without the use of a queue though. I'm still something of a NodeJS novice but I'd guess that reading/processing every chunk inside a process.nextTick() callback would cause more disk IO problems than memory ones.
When I get the app running I might do some load-testing, the results would be very interesting.
Just curious, but does that implementation use the native websocket if possible, and then falls back on Flash if needed? I am interested in such a framework.
One nice find from the article is the link to the Flash implementation of websockets: http://github.com/gimite/web-socket-js