I\'m sure Wave doesn\'t poll the server every millisecond to find out if the other user has typed something... so how can I see what the other person is typing as they type? And
the entire reason for WebSockets is to have the browser keep a bi-directional socket open to a server so that real time communications can be used. When someone types on the other end, in a wave client, it triggers an event that is sent to the server and the server in turn looks to see who should also receive the event and pass them the event, in this case the typed letter.
WebSocket and Comet are different.
Granville