Hyper Text Coffee Pot Control Protocol

A working teapot at , which implements the protocol as a server.
Implementation of HTCPCP at http://error418.net/.

The Hyper Text Coffee Pot Control Protocol (HTCPCP) is a facetious communications protocol for controlling, monitoring, and diagnosing coffee pots. It is specified in RFC 2324, published on 1 April 1998 as an April Fools' Day RFC,[1] as part of an April Fools prank.[2] An extension is published as RFC 7168 on 1 April 2014[3] to support brewing teas, which is also an April Fools' Day RFC.

Protocol

RFC 2324 was written by Larry Masinter, who describes it as a satire, saying "This has a serious purpose – it identifies many of the ways in which HTTP has been extended inappropriately."[4] The wording of the protocol made it clear that it was not entirely serious; for example, it notes 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 client side implementation of it,[5] and a number of bug reports exist complaining about Mozilla’s lack of support for the protocol.[6] Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in RDF"[7] in parody of the World Wide Web Consortium's (W3C) "HTTP Vocabulary in RDF".[8]

On April 1, 2014, RFC 7168 extended HTCPCP to fully handle teapots.[3]

Commands and replies

HTCPCP is an extension of HTTP. HTCPCP requests are identified with the uniform resource identifier (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 POSTCauses the HTCPCP server to brew coffee. Using POST for this purpose is deprecated. A new HTTP Request header field "Accept-Additions" is proposed, supporting optional additions including Cream, Whole-milk, Vanilla, Raspberry, Whisky, Aquavit, etc.
GETRetrieves coffee from the HTCPCP server.
PROPFINDFinds out metadata about the coffee.
WHENSays "when", causing the HTCPCP server to stop pouring milk into the coffee (if applicable).

It also defines two error responses:

406 Not AcceptableThe HTCPCP server is unable to provide the requested addition for some reason; the response should indicate a list of available additions. The RFC observes that "In practice, most automated coffee pots cannot currently provide additions."
418 I'm a teapotThe HTCPCP server is a teapot; the resulting entity body may be short and stout. Demonstrations of this behaviour exist.[9][10][11][12]

See also

Wikimedia Commons has media related to Coffee pots.

References

  1. ↑ "Request for Comments 2324", Network Working Group, IETF
  2. ↑ DeNardis, Laura (30 September 2009). Protocol Politics: The Globalization of Internet Governance. MIT Press. pp. 27ff. ISBN 978-0-262-04257-4. Retrieved 8 May 2012.
  3. 1 2 "Request for Comments 7168", The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA), IETF
  4. ↑ Larry Masinter. "IETF RFCs". Archived from the original on 2013-04-11.
  5. ↑ "Emacs extension: coffee.el", Emarsden, Chez.
  6. ↑ "Bug 46647 – (coffeehandler) HTCPCP not supported (RFC2324)", Bugzilla, Mozilla
  7. ↑ HTCPCP Vocabulary in RDF – WC3 RFC Draft, Chief Arabica (Web-Controlled Coffee Consortium, 1 April 2008, retrieved 17 August 2009
  8. ↑ Koch, Johannes (ed.), HTTP Vocabulary in RDF, et al, W3, retrieved 17 August 2009
  9. ↑ Reddington, Joseph, Illustrated implementation of Error 418
  10. ↑ Plain implementation of Error 418
  11. ↑ Raspberry Pi based implementation of Error 418
  12. ↑ A Goblin Teasmade teamaker with an implementation of Error 418

External links

This article is issued from Wikipedia - version of the Monday, December 21, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.