RFC6202 · Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes.
IETF · RFCОфициальная английская аннотация
On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes.
{
"id": "RFC6202",
"number": 6202,
"title_en": "Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, \"server- initiated\" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such \"bidirectional HTTP\" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes.",
"authors": [
"S. Loreto",
"P. Saint-Andre",
"S. Salsano",
"G. Wilkins"
],
"organizations": [],
"publication_date": "2011-04-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IETF",
"stream_ru": "IETF",
"area": "",
"area_ru": "",
"working_group": "NON WORKING GROUP",
"source_draft": "draft-loreto-http-bidirectional-07",
"page_count": 19,
"doi": "10.17487/RFC6202",
"keywords": [
"Hypertext Transfer Protocol",
"bidirectional HTTP",
"HTTP long polling",
"HTTP streaming"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc6202/",
"html": "https://www.rfc-editor.org/rfc/rfc6202.html",
"txt": "https://www.rfc-editor.org/rfc/rfc6202.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc6202/"
}
}