I bet WebSockets are much faster. So if I want to use lots of ajax continuously, WebSockets are recommended as an alternative?
A:
I think is not a issue of speed, is a issue of comunication and real time process
diegueus9
2010-06-28 15:08:56
Yeah I meant real time process, like a chat that has more special features that require even more communication with the server.
Zippo
2010-06-28 15:12:13
The problem with websockets is that are experimental, and a draft, not full supported by all webbrowsers
diegueus9
2010-07-06 12:55:38
+1
A:
Ajax is slower because the overhead. But Ajax is more compatible, Websocket is currently a bit experimental and it is not widely supported by most browser.
magallanes
2010-06-28 15:10:16
A:
If you're in regular need of asynchronous data transmission I'd say you should try out websockets, it's really easy to use. One problem is - because of the early stage - the websocket interface might change (which has happended already) and render your web application unusable until you update your code.
bennedich
2010-06-30 16:58:18
+2
A:
It's two different technology things. With AJAX client just send request to server and wait to response. Websocket is HTML5 implementation for Comet technology, the idea is push information from server to client.
Boris
2010-06-30 17:24:15