Compare Revisions

Connection management in HTTP/1.x

Revision 1120501 by bunnybooboo on September 18, 2016 at 7:08:01 AM PDT

Revision 1121443 by bunnybooboo on September 19, 2016 at 3:39:58 PM PDT

Title:

Connection management in HTTP/1.x

Slug:

Web/HTTP/Connection_management_in_HTTP_1.x

Tags:

"Guide" "HTTP" "Performance" "WebMechanics" "Performance"

Comment:

peristent connections editorial review

couple of grammatical edits

Content:

	Revision 1120501			Revision 1121443
n	66	In HTTP/1.1, peristence is the default, and the header is n	n	66	In HTTP/1.1, peristence is the default, and the header is n
	>	o longer needed (but often added in case of a fallback to HTTP/1.		>	o longer needed (but it is often added as a defensive measure aga
	>	0).		>	inst cases requiring a fallback to HTTP/1.0).
t	91	Pipelining is the functionality to send several requests su	t	91	Pipelining is the functionality to send several requests su
	>	ccessively over the same persistent connection without waiting fo		>	ccessively, over the same persistent connection, without waiting
	>	r the answer. That way the latency of the connection is avoided.		>	for the answer. This way the latency of the connection is avoided
	>	Theoretically, performance could also be improved if two HTTP req		>	. Theoretically, performance could also be improved if two HTTP r
	>	uests could be packed into the same TCP message. The typical <a h		>	equests could be packed into the same TCP message. The typical <a
	>	ref="https://en.wikipedia.org/wiki/Maximum_segment_size">MSS</a>		>	href="https://en.wikipedia.org/wiki/Maximum_segment_size">MSS</a
	>	(Maximum Segment Size), is big enough to contain several simple r		>	> (Maximum Segment Size), is big enough to contain several simple
	>	equests, although the size of HTTP requests grow over the years.		>	requests, although the size of HTTP requests grow over the years
				>	.