AJAX and websocket are two very different technologies, but at a basic level you can think of websocket as a "superset" of AJAX. AJAX enables client-server interaction, but all activity must originate on the client side (the server cannot push any data to a client without first being prompted to do so). Websocket is a fully bi-directional protocol. Everything you can do with AJAX, you could implement in websocket, but not the other way around. That said, websocket is not a replacement for AJAX. Websocket requires an active connection to be maintained between the client and server, which will incur some overhead, while AJAX does not. My inclination is to say to use AJAX by default unless you need to use websocket.
On Monday, January 21, 2013 6:46:53 AM UTC-5, Chrystopher Medina wrote: > > my friend do u think that websockets is gonna replace to ajax. or both of > them are two diferent things > ....can u give me some links in order to learn more about ajax and > websockets -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/A3SPDG4_L0QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
