> Node.js is ideal for such routing/switching based interactions where it takes data from one end, pumps it to the other and does the reverse.
I've been intrigued by node.js since it comes up on HN so much, but this has really got me interested as this describes exactly a portion of a project I'm working on right now. In my case, the data would be copious and binary rather than instant message text -- anyone know if node.js is performant enough to handle that case?