TCP - Revision history

DoesItReallyMatter: Magic links are deprecated

2019-02-22T06:01:46Z

← Older revision		Revision as of 06:01, 22 February 2019
Line 1:		Line 1:
	{{Wikipedia\|TCP}}		{{Wikipedia\|TCP}}
	'''TCP''' stands for '''Transmission Control Protocol'''. It is a connection-oriented, reliable delivery byte-stream transport layer communication [[protocol]], currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.		'''TCP''' stands for '''Transmission Control Protocol'''. It is a connection-oriented, reliable delivery byte-stream transport layer communication [[protocol]], currently documented in [https://tools.ietf.org/html/rfc793 IETF RFC 793]. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.

	TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP ([[VoIP]]). In many cases, the User Datagram Protocol ([[UDP]]) may be used in place of TCP when just application multiplexing services are required.		TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP ([[VoIP]]). In many cases, the User Datagram Protocol ([[UDP]]) may be used in place of TCP when just application multiplexing services are required.

	[[Category:Protocols]]		[[Category:Protocols]]

DoesItReallyMatter: Prune dead external links, add wikilinks

2019-01-31T07:02:21Z

Prune dead external links, add wikilinks

← Older revision		Revision as of 07:02, 31 January 2019
Line 1:		Line 1:
	TCP stands for Transmission Control Protocol. It is a connection-oriented, reliable delivery byte-stream transport layer communication protocol, currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.		{{Wikipedia\|TCP}}
			'''TCP''' stands for '''Transmission Control Protocol'''. It is a connection-oriented, reliable delivery byte-stream transport layer communication [[protocol]], currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.

	TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.		TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP ([[VoIP]]). In many cases, the User Datagram Protocol ([[UDP]]) may be used in place of TCP when just application multiplexing services are required.

	~~==External Links==~~
	~~[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]<br>~~
	~~[http://blog.webhosting.uk.com/2006/11/27/tcpip-application-protocols/ TCP/IP Application Protocols]~~

	[[Category:Protocols]]		[[Category:Protocols]]

Underground78: Vadalism Undo revision 15315

2010-01-12T06:29:01Z

Vadalism Undo revision 15315

← Older revision		Revision as of 06:29, 12 January 2010
Line 1:		Line 1:
	~~Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis~~		TCP stands for Transmission Control Protocol. It is a connection-oriented, reliable delivery byte-stream transport layer communication protocol, currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.

			TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.

			==External Links==
			[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]<br>
			[http://blog.webhosting.uk.com/2006/11/27/tcpip-application-protocols/ TCP/IP Application Protocols]

			[[Category:Protocols]]

Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis at 02:08, 12 January 2010

2010-01-12T02:08:08Z

← Older revision		Revision as of 02:08, 12 January 2010
Line 1:		Line 1:
	TCP stands for Transmission Control Protocol. It is a connection-oriented, reliable delivery byte-stream transport layer communication protocol, currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.		Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis

	TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.

	~~==External Links==~~
	~~[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]<br>~~
	~~[http://blog.webhosting.uk.com/2006/11/27/tcpip-application-protocols/ TCP/IP Application Protocols]~~

	~~[[Category:Protocols]]~~

Josh-A: /* External Links */

2007-09-29T08:05:22Z

External Links

← Older revision		Revision as of 08:05, 29 September 2007
Line 4:		Line 4:

	==External Links==		==External Links==
	[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]		[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]<br>
			[http://blog.webhosting.uk.com/2006/11/27/tcpip-application-protocols/ TCP/IP Application Protocols]

	[[Category:Protocols]]		[[Category:Protocols]]

H2g2bob: Formatting

2006-10-08T12:49:43Z

Formatting

← Older revision		Revision as of 12:49, 8 October 2006
Line 2:		Line 2:

	TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.		TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.

			==External Links==
			[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]

	[[Category:Protocols]]		[[Category:Protocols]]


	~~'''External Links'''~~

	~~[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]~~

RyanW at 12:24, 7 October 2006

2006-10-07T12:24:52Z

← Older revision		Revision as of 12:24, 7 October 2006
Line 8:		Line 8:
	'''External Links'''		'''External Links'''

	~~TCP general Information:~~http://blog.eukhost.com/2006/06/08/tcp		[http://blog.eukhost.com/2006/06/08/tcp TCP general Information]

RyanW at 12:23, 7 October 2006

2006-10-07T12:23:17Z

← Older revision		Revision as of 12:23, 7 October 2006
Line 4:		Line 4:

	[[Category:Protocols]]		[[Category:Protocols]]


			'''External Links'''

			TCP general Information:http://blog.eukhost.com/2006/06/08/tcp

H2g2bob at 20:42, 15 January 2006

2006-01-15T20:42:45Z

← Older revision		Revision as of 20:42, 15 January 2006
Line 2:		Line 2:

	TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.		TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.

			[[Category:Protocols]]

EdddMy at 23:08, 26 February 2005

2005-02-26T23:08:23Z

← Older revision		Revision as of 23:08, 26 February 2005
Line 1:		Line 1:
	TCP stands for Transmission Control Protocol.		TCP stands for Transmission Control Protocol. It is a connection-oriented, reliable delivery byte-stream transport layer communication protocol, currently documented in IETF RFC 793. During the data transfer phase, a number of key mechanisms determine TCP's reliability and robustness. These include using sequence numbers for ordering received TCP segments and detecting duplicate data, checksums for segment error detection, and acknowledgements and timers for detecting and adjusting to loss or delay.

			TCP is not appropriate for many applications as for example, real-time applications. They often don't need, and will suffer from TCP's reliable delivery mechanisms. In those types of applications it is often better to deal with some loss, errors or congestion than to try to adjust for them. Example applications that do not typically use TCP include multimedia streaming, real-time multiplayer games and voice over IP (VoIP). In many cases, the User Datagram Protocol (UDP) may be used in place of TCP when just application multiplexing services are required.