Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Connectionless communication
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Attributes== Under connectionless communication between two network [[Communication endpoint|endpoints]], a message can be sent from one endpoint to another without prior arrangement. The device at one end of the communication transmits data addressed to the other, without first ensuring that the recipient is available and ready to receive the data. Some protocols allow for error correction by requesting retransmission. Connectionless protocols are [[stateless protocol]]s because the endpoints have no protocol-defined way to remember where they are in a "conversation" of message exchanges. It has lower [[Overhead_information|overhead]] than [[connection-oriented communication]] because, in connection-oriented communication, the communicating peers must first establish a logical or physical data channel or ''connection'' in a dialog preceding the exchange of user data. It allows for [[multicast]] and [[Broadcasting (networking)|broadcast]] operations in which the same data are transmitted to several recipients in a single transmission. In connectionless transmissions the service provider usually cannot guarantee that there will be no loss, [[error]] insertion, misdelivery, duplication, or out-of-[[sequence]] delivery of the packet. However, the effect of errors may be reduced by implementing error correction within an application protocol. In connectionless mode, there is less opportunity for optimization when sending several data units between the same two peers. By establishing a connection at the beginning of such a data exchange the components ([[Router (computing)|router]]s, [[Network bridge|bridges]]) along the network path would be able to pre-compute (and hence [[cache (computing)|cache]]) routing-related information, avoiding re-computation for every packet. In connection-oriented communication, network components can also reserve capacity for the transfer of the subsequent data units of a video download, for example.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)