Hyper Text Coffee Pot Control Protocol: Difference between revisions
Mrmagoo2006 (talk | contribs) |
Making a mention of theInternet of Things, which this is clearly a precursor to it. |
||
Line 3: | Line 3: | ||
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,<ref>[http://emarsden.chez.com/downloads/ Emacs extension: coffee.el]</ref> and a number of bug reports exist complaining about [[Mozilla|Mozilla's]] lack of support for the protocol.<ref>[https://bugzilla.mozilla.org/show_bug.cgi?id=46647 Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)] at bugzilla.mozilla.org</ref> Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in [[Resource Description Framework|RDF]]"<ref>Chief Arabica (Web-Controlled Coffee Consortium): [http://purl.org/NET/error404/xp/HTCPCP-in-RDF/ HTCPCP Vocabulary in RDF – WC3 RFC Draft 01 April 2008]. Accessed 17 August 2009.</ref> in analogy of the [[World Wide Web Consortium]]'s (W3C) "HTTP Vocabulary in RDF".<ref>Johannes Koch et al (editors): "[http://www.w3.org/TR/HTTP-in-RDF/ HTTP Vocabulary in RDF]". Accessed 17 August 2009.</ref> |
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,<ref>[http://emarsden.chez.com/downloads/ Emacs extension: coffee.el]</ref> and a number of bug reports exist complaining about [[Mozilla|Mozilla's]] lack of support for the protocol.<ref>[https://bugzilla.mozilla.org/show_bug.cgi?id=46647 Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)] at bugzilla.mozilla.org</ref> Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in [[Resource Description Framework|RDF]]"<ref>Chief Arabica (Web-Controlled Coffee Consortium): [http://purl.org/NET/error404/xp/HTCPCP-in-RDF/ HTCPCP Vocabulary in RDF – WC3 RFC Draft 01 April 2008]. Accessed 17 August 2009.</ref> in analogy of the [[World Wide Web Consortium]]'s (W3C) "HTTP Vocabulary in RDF".<ref>Johannes Koch et al (editors): "[http://www.w3.org/TR/HTTP-in-RDF/ HTTP Vocabulary in RDF]". Accessed 17 August 2009.</ref> |
||
The possibility and practicalness of the HTCPCP and coffee pots implementing it are now rising back into the notice of the industry, as the [[Internet of Things]] rose into fame. |
|||
==Commands and replies== |
==Commands and replies== |
||
Line 26: | Line 28: | ||
{{Commons category|Coffee pots}} |
{{Commons category|Coffee pots}} |
||
*[[Trojan Room coffee pot]] |
*[[Trojan Room coffee pot]] |
||
*[[Internet of Things]] |
|||
==References== |
==References== |
Revision as of 15:57, 4 July 2012
![](http://upload.wikimedia.org/wikipedia/commons/thumb/4/4d/HTCPCP_Pot.jpg/220px-HTCPCP_Pot.jpg)
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, "there is a strong, dark, rich requirement for a protocol designed espressoly [sic] for the brewing of coffee" that included a pun on the word "espresso."
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 practicalness of the HTCPCP and coffee pots implementing it are now rising back into the notice of the industry, as the Internet of Things rose into fame.
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 may be short and stout. Demonstrations of this behaviour exist.[7][8][9] |
See also
![](http://upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/30px-Commons-logo.svg.png)
References
- ^ Network Working Group – Request for Comments: 2324
- ^ Laura DeNardis (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
- ^ Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324) at bugzilla.mozilla.org
- ^ Chief Arabica (Web-Controlled Coffee Consortium): HTCPCP Vocabulary in RDF – WC3 RFC Draft 01 April 2008. Accessed 17 August 2009.
- ^ Johannes Koch et al (editors): "HTTP Vocabulary in RDF". Accessed 17 August 2009.
- ^ Illustrated implementation of Error 418 on BBC CBeebies
- ^ Illustrated implementation of Error 418
- ^ Plain implementation of Error 418