>_Web Socket or HTTP. What should you choose?

Posted 1 month ago  36 reads  

Author: Martin Fietkiewicz

In realtime applications we need information from our servers as soon as it’s available – and, fundamentally, the classic HTTP request/response paradigm isn’t up to the job. The server will be silent, new data or not, unless or until a consumer requests an update. That limitation saw the emergence of all manner of hacks and workarounds as devs sought to adapt that request/responsual model to a more dynamic, realtime web. These approaches actually work quite well in specific use cases, Gmail chat for instance. Problems emerge in low-latency applications or at scale, mainly because of the processing demands associated with HTTP.

Source: Read more on ably.com

Powered by HashtagCms.org