Hyper Text Coffee Pot Control Protocol: Difference between revisions
m Dating maintenance tags: {{Fact}} |
No edit summary |
||
Line 1: | Line 1: | ||
[[File:HTCPCP Pot.jpg|thumb|A server at http://134.219.188.123/, which implements the protocol.]] |
[[File:HTCPCP Pot.jpg|thumb|A server at http://134.219.188.123/, which implements the protocol.]] |
||
[[File:Htcpcp teapot.jpg|thumb|Implementation of HTCPCP at http://error418.net/.]] |
|||
The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''' for short) is a [[communications protocol]] for controlling, monitoring, and diagnosing [[coffee pot]]s. It is specified in [[Request for Comments|RFC]] 2324, published on [[April Fools' Day Request for Comments| 1 April]] 1998<ref>{{Citation | url = http://tools.ietf.org/html/rfc2324 | title = Network Working Group | contribution = Request for Comments 2324 | publisher = [[Internet Engineering Task Force | IETF]]}}.</ref> as part of an April Fools prank.<ref name= "DeNardis2009">{{cite book| first =Laura | last = DeNardis|title= Protocol Politics: The Globalization of Internet Governance|url= http://books.google.com/books?id=Secqz0XQJIsC&pg=PA27|accessdate=8 May 2012|date=30 September 2009|publisher=MIT Press|isbn=978-0-262-04257-4|pages=27–}}</ref> The wording of the protocol made it clear that it wasn't entirely serious; noting, for example, that "there is a strong, dark, rich requirement for a protocol designed [[espresso]]ly [sic] for the brewing of coffee". |
The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''' for short) is a [[communications protocol]] for controlling, monitoring, and diagnosing [[coffee pot]]s. It is specified in [[Request for Comments|RFC]] 2324, published on [[April Fools' Day Request for Comments| 1 April]] 1998<ref>{{Citation | url = http://tools.ietf.org/html/rfc2324 | title = Network Working Group | contribution = Request for Comments 2324 | publisher = [[Internet Engineering Task Force | IETF]]}}.</ref> as part of an April Fools prank.<ref name= "DeNardis2009">{{cite book| first =Laura | last = DeNardis|title= Protocol Politics: The Globalization of Internet Governance|url= http://books.google.com/books?id=Secqz0XQJIsC&pg=PA27|accessdate=8 May 2012|date=30 September 2009|publisher=MIT Press|isbn=978-0-262-04257-4|pages=27–}}</ref> The wording of the protocol made it clear that it wasn't entirely serious; noting, for example, that "there is a strong, dark, rich requirement for a protocol designed [[espresso]]ly [sic] for the brewing of coffee". |
||
Revision as of 21:08, 14 February 2013
The Hyper Text Coffee Pot Control Protocol (HTCPCP for short) is a communications protocol for controlling, monitoring, and diagnosing coffee pots. It is specified in RFC 2324, published on 1 April 1998[1] as part of an April Fools prank.[2] The wording of the protocol made it clear that it wasn't entirely serious; noting, for example, that "there is a strong, dark, rich requirement for a protocol designed espressoly [sic] for the brewing of coffee".
Despite the joking nature of its origins, or perhaps because of it, the protocol has remained as a minor presence online. The editor Emacs includes a fully functional implementation of it,[3] and a number of bug reports exist complaining about Mozilla’s lack of support for the protocol.[4] Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in RDF"[5] in analogy of the World Wide Web Consortium's (W3C) "HTTP Vocabulary in RDF".[6]
The possibility and practicality of the HTCPCP and coffee pots implementing it are now rising back into the notice of the industry, as the Internet of Things rises into fame.[citation needed]
Commands and replies
HTCPCP is an extension of HTTP. HTCPCP requests are identified with the URI scheme coffee:
(or the corresponding word in any other of the 29 listed languages) and contain several additions to the HTTP methods:
BREW or POST |
Causes the HTCPCP server to brew coffee. |
GET |
Retrieves coffee from the HTCPCP server. |
PROPFIND |
Finds out metadata about the coffee. |
WHEN |
Says "when", causing the HTCPCP server to stop pouring milk into the coffee (if applicable). |
It also defines two error responses:
406 Not Acceptable |
The HTCPCP server is unable to brew coffee for some reason; the response should indicate a list of acceptable coffee types. |
418 I'm a teapot |
The HTCPCP server is a teapot; the resulting entity body may be short and stout. Demonstrations of this behaviour exist.[7][8][9] |
See also
References
- ^ "Request for Comments 2324", Network Working Group, IETF.
- ^ DeNardis, Laura (30 September 2009). Protocol Politics: The Globalization of Internet Governance. MIT Press. pp. 27–. ISBN 978-0-262-04257-4. Retrieved 8 May 2012.
- ^ "Emacs extension: coffee.el", Emarsden, Chez.
- ^ "Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)", Bugzilla, Mozilla.
- ^ HTCPCP Vocabulary in RDF – WC3 RFC Draft, Chief Arabica (Web-Controlled Coffee Consortium, 1 April 2008, retrieved 17 August 2009.
- ^ Koch, Johannes (ed.), HTTP Vocabulary in RDF, et al, W3, retrieved 17 August 2009.
- ^ Illustrated implementation of Error 418, UK: RHUL
{{citation}}
:|first=
missing|last=
(help). - ^ Plain implementation of Error 418.
- ^ Raspberry Pi based implementation of Error 418.