Joe Armstrong has a good argument for websockets as the next phase of web development at armstrong: Comet is dead long live websockets:
I think this means the death of the following technologies:
- keep-alive sockets
All the above are merely hacks, inadequate ways of programming round the central problem that web-browsers could not simply open a socket and do asynchronous I/O like any other regular application.
His example uses Erlang, but the same idea applies with Resin’s WebSocket support