From LIMSWiki
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

BEEP (an acronym for Blocks Extensible Exchange Protocol) is a framework for creating network application protocols.[1] BEEP is intended to abstract out the common features that have traditionally been duplicated in each protocol implementation[2], including but not limited to[3]:

  • 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.[4]

Beep also incorporates the use of XML during channel management; "BEEP takes care of protocol infrastructure, [and] XML takes care of data structuring."[4] 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."[4] 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.[2]

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 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.[1] However, at that time BEEP was known as BXXP:

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.[2]

Requests for comments (RFCs) were generated in early 2001 for the protocol and its mapping onto TCP.[5]

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[6] — in general the BEEP protocol never saw major adoption.[7]

External links


An element or two of this article is reused from the Wikipedia article.


  1. 1.0 1.1 Marsan, Carolyn Duffy (26 June 2000). "'HTTP on steroids' to ease protocol work". Network World Fusion. Archived from the original on 02 April 2012. Retrieved 18 August 2014. 
  2. 2.0 2.1 2.2 "BEEP: General Questions". 3 February 2009. Retrieved 18 August 2014. 
  3. Rose, Marshall (June 2002). "An Overview of BEEP". The Internet Protocol Journal 5 (2). Retrieved 18 August 2014. 
  4. 4.0 4.1 4.2 Dumbill, Edd (1 December 2001). "XML Watch: Bird's-eye BEEP". developerWorks. IBM. Archived from the original on 28 February 2009. Retrieved 18 August 2014. 
  5. "RFC 3080: The Blocks Extensible Exchange Protocol Core". IETF. March 2001. Retrieved 19 August 2014. 
  6. Côté, Daniel (7 January 2004). "XGrid". Simple. Archived from the original on 21 February 2009. Retrieved 19 August 2014. 
  7. Münch, Robert M. (4 January 2013). "D based BEEP library?". D Programming Language Discussion. Archived from the original on 19 August 2014.$lag$ Retrieved 19 August 2014.