>>Node uses single application thread and uses ansynchronous scheduling to IO bound operations to distributed load....
>
>Thank you for your that explanation, Rick. Most helpful and thought provoking. This very clearly clarifies the position of node.js from a strategic point of view, exactly what I was trying to find out.
>
>Sounds to me like node.js may be a good fit for dealing with simple AJAX requests as long as they don't involve any complicated processing. Of course the next thought, bearing in mind this is quite a major drawback, is whether node.js could become multi-threaded in a future version? This wouldn't mean leaving the whole Async paradigm behind, just allowing it to be configured to run multiple separate instances of node.js at the same time.

That is the gimmick of vert.x implementing asynch server somewhat inspired by node.js in Java. Kills off re-use of clientside source,but such is generated sometimes IAC.