BEEP - Revision history

Shawndouglas: Internal link

2014-08-22T17:03:57Z

Internal link

← Older revision		Revision as of 17:03, 22 August 2014
Line 12:		Line 12:
	BEEP typically runs on top of TCP and allows the exchange of messages over a channel. Unlike HTTP (and similar protocols), either end of the connection can communicate at any time, with messages being interleaved easily. BEEP also includes facilities for encryption and authentication and is highly extensible.<ref name="IBMBEEP">{{cite web \|url=http://ibm.com/developerworks/webservices/library/x-beep \|archiveurl=https://web.archive.org/web/20090228022105/http://ibm.com/developerworks/webservices/library/x-beep \|title=XML Watch: Bird's-eye BEEP \|work=developerWorks \|author=Dumbill, Edd \|publisher=IBM \|date=01 December 2001 \|archivedate=28 February 2009 \|accessdate=18 August 2014}}</ref>		BEEP typically runs on top of TCP and allows the exchange of messages over a channel. Unlike HTTP (and similar protocols), either end of the connection can communicate at any time, with messages being interleaved easily. BEEP also includes facilities for encryption and authentication and is highly extensible.<ref name="IBMBEEP">{{cite web \|url=http://ibm.com/developerworks/webservices/library/x-beep \|archiveurl=https://web.archive.org/web/20090228022105/http://ibm.com/developerworks/webservices/library/x-beep \|title=XML Watch: Bird's-eye BEEP \|work=developerWorks \|author=Dumbill, Edd \|publisher=IBM \|date=01 December 2001 \|archivedate=28 February 2009 \|accessdate=18 August 2014}}</ref>

	Beep also incorporates the use of XML during channel management; "BEEP takes care of protocol infrastructure, [and] XML takes care of data structuring."<ref name="IBMBEEP" /> XML has also been used to encode messages, meaning "any existing messaging standard defined in terms of XML documents has a reasonably straightforward mapping into a BEEP profile."<ref name="IBMBEEP" /> However, BEEP profiles aren't required to use XML for encoding, meaning the use of XML could technically be limited to the beginning of a session.<ref name="BEEPFAQ" />		Beep also incorporates the use of [[XML]] during channel management; "BEEP takes care of protocol infrastructure, [and] XML takes care of data structuring."<ref name="IBMBEEP" /> XML has also been used to encode messages, meaning "any existing messaging standard defined in terms of XML documents has a reasonably straightforward mapping into a BEEP profile."<ref name="IBMBEEP" /> However, BEEP profiles aren't required to use XML for encoding, meaning the use of XML could technically be limited to the beginning of a session.<ref name="BEEPFAQ" />

	BEEP includes a number of built-in features, including an initial handshake protocol, authentication, security, and error handling. Using BEEP, one can create new protocols for a variety of applications, including instant messaging, file transfer, content syndication, and network management.		BEEP includes a number of built-in features, including an initial handshake protocol, authentication, security, and error handling. Using BEEP, one can create new protocols for a variety of applications, including instant messaging, file transfer, content syndication, and network management.

Shawndouglas: /* References */ Added cat

2014-08-22T16:29:55Z

References: Added cat

← Older revision		Revision as of 16:29, 22 August 2014
Line 38:		Line 38:
	==References==		==References==
	<references />		<references />

			<!---Place all category tags here-->
			[[Category:Software and hardware terms]]

Shawndouglas: Added content.

2014-08-19T17:13:13Z

Added content.

← Older revision		Revision as of 17:13, 19 August 2014
Line 17:		Line 17:

	==History==		==History==
			BEEP was originally designed in 1999/2000 by Marshall Rose, the author of protocols such as POP3, SMTP, and SNMP. The IETF (Internet Engineering Task Force) took interest in the protocol in the spring of 2000, creating a working group to standardize the protocol.<ref name="BEEP00" /> However, at that time BEEP was known as BXXP:

	~~BEEP~~ was ~~designed by Marshall Rose~~, ~~who also worked~~ on the ~~POP3~~, ~~SMTP~~, ~~and SNMP protocols~~.		<blockquote>At the time, the letter "X" was pretty much de rigueur in any new technology. However, "X" isn't the first letter in "Extensible" and "Exchange," and further, BEEP has much more comic potential. So the IETF working group on BXXP renamed it BEEP.<ref name="BEEPFAQ" /></blockquote>

			Requests for comments (RFCs) were generated in early 2001 for the protocol and its mapping onto TCP.<ref name="RFC3080">{{cite web \|url=http://www.ietf.org/rfc/rfc3080.txt?number=3080 \|title=RFC 3080: The Blocks Extensible Exchange Protocol Core \|publisher=IETF \|date=March 2001 \|accessdate=19 August 2014}}</ref>

			Though a few high-profile applications of BEEP were implemented — including the 2004 release of Apple's XGrid, a distributed computing protocol that allows networked computers to contribute to a single task<ref name="XGrid">{{cite web \|url=http://unu.novajo.ca/simple/archives/000022.html \|archiveurl=https://web.archive.org/web/20090221012530/http://unu.novajo.ca/simple/archives/000022.html \|title=XGrid \|author=Côté, Daniel \|work=Simple \|date=07 January 2004 \|archivedate=21 February 2009 \|accessdate=19 August 2014}}</ref> — in general the BEEP protocol never saw major adoption.<ref name="BEEPMunch">{{cite web \|url=http://forum.dlang.org/thread/kc7ph3$lag$1@digitalmars.com \|archiveurl=https://web.archive.org/web/20140819170619/http://forum.dlang.org/thread/kc7ph3$lag$1@digitalmars.com \|title=D based BEEP library? \|work=D Programming Language Discussion \|author=Münch, Robert M. \|date=04 January 2013 \|archivedate=19 August 2014 \|accessdate=19 August 2014}}</ref>

	==External links==		==External links==
Line 27:		Line 32:
	* [http://www.ietf.org/rfc/rfc3081.txt?number=3081 IETF RFC #3081: Mapping the BEEP Core onto TCP]		* [http://www.ietf.org/rfc/rfc3081.txt?number=3081 IETF RFC #3081: Mapping the BEEP Core onto TCP]
	* [http://www.ietf.org/rfc/rfc3117.txt?number=3117 IETF RFC #3117: On the Design of Application Protocols], design considerations of the original BXXP protocol		* [http://www.ietf.org/rfc/rfc3117.txt?number=3117 IETF RFC #3117: On the Design of Application Protocols], design considerations of the original BXXP protocol

			==Notes==
			An element or two of this article is reused from [http://en.wikipedia.org/wiki/BEEP the Wikipedia article].

	==References==		==References==
	<references />		<references />

Shawndouglas: Created stub record. Saving and adding more tomorrow.

2014-08-19T02:37:11Z

Created stub record. Saving and adding more tomorrow.

New page

'''BEEP''' (an acronym for '''Blocks Extensible Exchange Protocol''') is a framework for creating network application protocols.<ref name="BEEP00">{{cite web |url=http://www.networkworld.com/news/2000/0626bxxp.html |archiveurl=https://web.archive.org/web/20120402165038/http://www.networkworld.com/news/2000/0626bxxp.html |title='HTTP on steroids' to ease protocol work |author=Marsan, Carolyn Duffy |work=Network World Fusion |date=26 June 2000 |archivedate=02 April 2012 |accessdate=18 August 2014}}</ref> BEEP is intended to abstract out the common features that have traditionally been duplicated in each protocol implementation<ref name="BEEPFAQ">{{cite web |url=http://www.beepcore.org/faq.html |title=BEEP: General Questions |publisher=BEEPCore.org |date=03 February 2009 |accessdate=18 August 2014}}</ref>, including but not limited to<ref name="BEEPOver">{{cite journal |url=http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_5-2/beep.html |journal=The Internet Protocol Journal |title=An Overview of BEEP |author=Rose, Marshall |volume=5 |issue=2 |date=June 2002 |accessdate=18 August 2014}}</ref>:

* framing messages;
* encoding data;
* negotiating capabilities;
* negotiating connection release;
* correlating requests and responses;
* handling multiple outstanding requests;
* handling multiple asynchronous requests; and
* providing integrated and modular security.

BEEP typically runs on top of TCP and allows the exchange of messages over a channel. Unlike HTTP (and similar protocols), either end of the connection can communicate at any time, with messages being interleaved easily. BEEP also includes facilities for encryption and authentication and is highly extensible.<ref name="IBMBEEP">{{cite web |url=http://ibm.com/developerworks/webservices/library/x-beep |archiveurl=https://web.archive.org/web/20090228022105/http://ibm.com/developerworks/webservices/library/x-beep |title=XML Watch: Bird's-eye BEEP |work=developerWorks |author=Dumbill, Edd |publisher=IBM |date=01 December 2001 |archivedate=28 February 2009 |accessdate=18 August 2014}}</ref>

Beep also incorporates the use of XML during channel management; "BEEP takes care of protocol infrastructure, [and] XML takes care of data structuring."<ref name="IBMBEEP" /> XML has also been used to encode messages, meaning "any existing messaging standard defined in terms of XML documents has a reasonably straightforward mapping into a BEEP profile."<ref name="IBMBEEP" /> However, BEEP profiles aren't required to use XML for encoding, meaning the use of XML could technically be limited to the beginning of a session.<ref name="BEEPFAQ" />

BEEP includes a number of built-in features, including an initial handshake protocol, authentication, security, and error handling. Using BEEP, one can create new protocols for a variety of applications, including instant messaging, file transfer, content syndication, and network management.

==History==

BEEP was designed by Marshall Rose, who also worked on the POP3, SMTP, and SNMP protocols.

==External links==

* [http://www.beepcore.org/index.html BEEP Community Site]
* [http://www.aspl.es/vortex/ Vortex Library], a C implementation library of BEEP
* [http://www.ietf.org/rfc/rfc3080.txt?number=3080 IETF RFC #3080: The Blocks Extensible Exchange Protocol Core]
* [http://www.ietf.org/rfc/rfc3081.txt?number=3081 IETF RFC #3081: Mapping the BEEP Core onto TCP]
* [http://www.ietf.org/rfc/rfc3117.txt?number=3117 IETF RFC #3117: On the Design of Application Protocols], design considerations of the original BXXP protocol

==References==
<references />