Two-way Communication over HTTP: Difference between revisions
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[HTTP#Subjects|HTTP]] | * [[HTTP#Subjects|HTTP]] | ||
* [[WebSocket#Overview|WebSockets]] | |||
=Overview= | =Overview= | ||
Browsers can receive simulated server-to-client invocations by using the following mechanisms: | Browsers can receive simulated server-to-client invocations by opening multiple HTTP connections and using the following mechanisms: | ||
* XMLHttpRequest | * XMLHttpRequest | ||
* <iframe>s and long polling | * <iframe>s and long polling | ||
The problem with this approach is that the server is forced a number of underlying TCP connections for each client: one for sending information and a new one for each incoming message. The Wie protocol has a high overhead, each message has a HTTP header. | |||
Obsoleted by [[WebSocket#Overview|WebSockets]]. | Obsoleted by [[WebSocket#Overview|WebSockets]]. | ||
Latest revision as of 19:59, 25 April 2018
Internal
Overview
Browsers can receive simulated server-to-client invocations by opening multiple HTTP connections and using the following mechanisms:
- XMLHttpRequest
- <iframe>s and long polling
The problem with this approach is that the server is forced a number of underlying TCP connections for each client: one for sending information and a new one for each incoming message. The Wie protocol has a high overhead, each message has a HTTP header.
Obsoleted by WebSockets.