Hyper Text Coffee Pot Control Protocol: Difference between revisions
replacing pic |
Vinithehat (talk | contribs) |
||
| Line 1: | Line 1: | ||
{{db-hoax}} |
|||
{{Tone|date=March 2012}} |
{{Tone|date=March 2012}} |
||
{{Context|date=March 2012}} |
{{Context|date=March 2012}} |
||
Revision as of 14:14, 8 May 2012
This article may meet Wikipedia's criteria for speedy deletion as a blatant hoax. This only applies to cases where the deception is so obvious as to constitute pure vandalism. Additionally, the mere fact that the page is about a hoax does not, on its own, qualify for speedy deletion. See CSD G3.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Vinithehat (contribs | logs) at 14:14, 8 May 2012 (UTC) (12 years ago) |
 | This article's tone or style may not reflect the encyclopedic tone used on Wikipedia. (March 2012) |
| This article provides insufficient context for those unfamiliar with the subject. (March 2012) |
The Hyper Text Coffee Pot Control Protocol (HTCPCP for short) is a protocol for controlling, monitoring, and diagnosing coffee pots.
HTCPCP is specified in RFC 2324, published on 1 April 1998.[1] The editor Emacs includes a fully functional implementation of it,[2] and a number of bug reports exist complaining about Mozilla's lack of support for the protocol.[3] Ten years after the publication of HTCPCP, the Web-Controlled Coffee Consortium (WC3) published a first draft of "HTCPCP Vocabulary in RDF"[4] in analogy of the World Wide Web Consortium's (W3C) "HTTP Vocabulary in RDF".[5]
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.[6][7][8] |
See also
References
- ^ Network Working Group – Request for Comments: 2324
- ^ 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.
- ^ HTTP 418 implemented on BBC CBeebies
- ^ Implementing Error 418
- ^ Error 418 implemented