Talk:Server-sent events
Add topic | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
| |||||||||||||||||||||
An incorrect sentence re: persistent connections
[edit]This sentence is manifestly WRONG.
"Since SSE does not use either persistent connections nor chunked transfer encoding, HTTP/1.1 is not a technical requirement."
A persistent connection is part of the raison d'etre of SSE and is required by the standard by the inclusion of techniques such as message "framing", "event ids" and mechanisms to "terminate" a clients reconnection attempts in the face of lower-level connectivity failure.
There is one scenario that might *suggest* the lack of an abstract persistent connection.
Clients are allowed to temporarily "hand off" management of a (persistent) connection to a proxy in "difficult" environments (mobile handsets, brief loss of connectivity, limited battery power, etc.). But even in this "edge case" the standard considers the client+proxy as collectively maintaining the "persistent connection."
"9.2.8 Connectionless push and other features User agents running in controlled environments, e.g. browsers on mobile handsets tied to specific carriers, may offload the management of the connection to a proxy on the network. In such a situation, the user agent for the purposes of conformance is considered to include both the handset software and the network proxy." PhillipWardHutto (talk) 03:31, 25 September 2025 (UTC)