RFC 2324:Hyper Text Coffee Pot Control Protocol (H...
RFC-Ref

server


Click on the red underlined text to get to the source

... HTTP 1.1 ([RFC2068]) permits the transfer of web objects from origin servers to clients. The web is world-wide. HTCPCP is based on HTTP. ...


... methods, header fields and return codes. All HTCPCP servers should be referred to with the "coffee:" URI scheme (Section 4). ...
... Commands to control a coffee pot are sent from client to coffee server using either the BREW or POST method, and a message body with ...
... A coffee pot server MUST accept both the BREW and POST method equivalently. However, the use of ...
... may depend, in fact, on conditions in the client rather than just in the server. Thus, this protocol includes an extension to the "Safe" response ...
... HTTP return codes are used to indicate difficulties of the HTCPCP server. This section identifies special interpretations and new return codes. ...


... the user's computer. Thus, if the user wants to return to that page, it is now stored locally and does not need to be requested again from the server. An image used for robot control or for monitoring a changing scene is dynamic. A fresh version ...
... changing scene is dynamic. A fresh version needs to be retrieved from the server each time it is accessed. ...


... video camera, and feed the images to a web server. This was an appropriate application of ATM ...



Google
Web
RFC-Ref