Content deleted Content added
No edit summary |
Reverting edit(s) by 103.170.228.58 (talk) to rev. 1221489598 by Wikipedialuva: Unexplained content removal (RW 16.1) |
||
(29 intermediate revisions by 18 users not shown) | |||
Line 1:
{{
A '''stateless protocol''' is a [[communication protocol]] in which the receiver must not retain [[Session (computer science)|session]] state from previous requests. The sender transfers relevant session state to the receiver in such a way that every request can be understood in isolation, that is without [[reference]] to session state from previous requests retained by the receiver.<ref>{{cite thesis |last=Fielding |first=Roy |date=2000 |title=Architectural Styles and the Design of Network-Based Software Architectures |type=Doctoral dissertation |publisher=University of California, Irvine |oclc=45706361 |url=https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm |section-url=https://www.ics.uci.edu/~fielding/pubs/dissertation/net_arch_styles.htm#sec_3_4_3 |section=3.4.3 Client-Stateless-Server (CSS) |access-date=2021-05-18}}</ref>
In [[computer network]]s, examples of stateless protocols include the [[Internet Protocol]] (IP), which is the foundation for the [[Internet]], and the [[Hypertext Transfer Protocol]] (HTTP), which is the foundation of the [[World Wide Web]]. Examples of stateful protocols include the [[Transmission Control Protocol]] (TCP) and the [[File Transfer Protocol]] (FTP).
Stateless protocols improve the properties of visibility, reliability, and scalability. Visibility is improved because a monitoring system does not have to look beyond a single request in order to determine its full nature. Reliability is improved because it eases the task of recovering from partial failures. Scalability is improved because not having to store session state between requests allows the [[Server (computing)|server]] to quickly free resources and further simplifies implementation.
The disadvantage of stateless protocols is that they may decrease network performance by increasing the repetitive data sent in a series of requests, since that data cannot be left on the server and reused.
== Examples ==
An
Contrast this with a traditional [[File Transfer Protocol|FTP]] server that conducts an interactive session with the user. During the session, a user is provided a means to be authenticated and set various variables (working directory, transfer mode), all stored on the server as part of the
== Stacking of stateless and stateful protocol layers ==
There can be complex interactions between stateful and stateless protocols among different protocol layers. For example, HTTP
This stacking of layers continues even above HTTP. As a workaround for the lack of a retained session
== See also ==
* [[Representational state transfer]]
* [[Soft state]]
== References ==
{{reflist}}
[[Category:Servers (computing)]]
|