This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Protocol Server
Protocol Server

Version management

Difference between version and

At line 1 added 6 lines
!!! Overview
When speaking about [Protocol] interactions, the [{$pagename}] is the receiver with [Protocol Client] which must initiate the [Protocol] Exchange.[Example] − Web Server ([{$pagename}]) keeps waiting for requests from [Internet] [Browsers] ([Protocol Client]) and as soon as it gets any request from a [browser], it picks up a requested [HTML] page and sends it back to that [Browser].Note that the [Protocol Client] needs to know the address of the [{$pagename}], but the [{$pagename}] does not need to know the address or even the existence of the [Protocol Client] prior to the [connection] being established. Once a [connection] is established, both sides can send and receive [data] using a [protocol].
!! [RFC 2616]
[RFC 2616] defines [{$pagename}] as service requests by sending back responses. Any given program may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general. Likewise, any [server] may act as an [Web Origin] [server], [proxy], [gateway], or tunnel, switching behavior based on the nature of each request.!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop