Hyper Text Coffee Pot Control Protocol: Difference between revisions

Content deleted Content added

Inline

Revision as of 08:45, 20 March 2005

The Hyper Text Coffee Pot Control Protocol (HTCPCP for short) is a protocol for controlling, monitoring and diagnosing coffee pots.

HTCPCP is specified in the jocular RFC 2324, published on April 1 1998. Although the RFC describing the protocol is an April fools joke and not to be taken seriously, it specifies the protocol itself accurately enough for it to be a real, non-fictional protocol. No known implementations of it exist, though.

HTCPCP is an extension of HTTP. HTCPCP requests are identified with the URI scheme coffee: 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).

For more detailed specifications, see the HTCPCP RFC.

Revision as of 01:51, 20 March 2005 edit JTN (talk \| contribs) Extended confirmed users 2,417 edits Category:Internet protocols; other tweaks ← Previous edit		Revision as of 08:45, 20 March 2005 edit undo JIP (talk \| contribs) Administrators 67,524 edits No edit summary Next edit →
Line 1:		Line 1:
	The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''' for short) is a [[protocol]] for controlling, monitoring and diagnosing [[coffee]] pots.		The '''Hyper Text Coffee Pot Control Protocol''' ('''HTCPCP''' for short) is a [[protocol (computing)\|protocol]] for controlling, monitoring and diagnosing [[coffee]] pots.

	HTCPCP is specified in the jocular RFC 2324, published on [[April 1]] [[1998]]. Although the [[Request For Comments\|RFC]] describing the protocol is an [[April fools]] joke and not to be taken seriously, it specifies the protocol itself accurately enough for it to be a real, non-fictional protocol. No known implementations of it exist, though.		HTCPCP is specified in the jocular RFC 2324, published on [[April 1]] [[1998]]. Although the [[Request For Comments\|RFC]] describing the protocol is an [[April fools]] joke and not to be taken seriously, it specifies the protocol itself accurately enough for it to be a real, non-fictional protocol. No known implementations of it exist, though.