New answers tagged websocket
ajax / html request Slowpoke. Good for loading pages without navigating to another url. No good for action games but should be fine for turn based games I imagine. The good thing is that the server only needs to handle one request at a time. So the server code is serial and not concurrent. This means it's a lot less complicated. Each request is often ...
Websockets are a very elegant and fast way to implement asynchronous communication between client and server. But they are far from the only. When low latency isn't that important for you, you can substitute it with XmlHttpRequest (aka "AJAX"). But for a real-time action-oriented game, WebSockets are usually the superior solution.
Top 50 recent answers are included