In computer networking, BEEP (Blocks Extensible Exchange Protocol) is a framework for creating network application protocols. It includes an application protocol kernel for connection-oriented asynchronous interactions, and can be used both for binary and text-based messages within the context of a single application user identity.
BEEP is intended to abstract-out the common features that have traditionally been duplicated in each protocol implementation. BEEP (formerly called BXXP) typically runs on top of TCP and allows the exchange of messages called 'frames'. Unlike HTTP (and similar protocols), either end of the connection can send a frame at any time, and 'questions' and 'replies' can be interleaved easily. BEEP also includes facilities for encryption and authentication, and is highly extensible.
One promising alternative to HTTP is the Blocks Extensible Exchange Protocol (BEEP).BEEP is a new IETF framework of best practices for building new protocols. BEEP is layered directly on TCP and 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: Blocks Extensible Exchange Protocol". http://www.javvin.com/protocolBEEP.html: Javvin network management and security. Archived from the original on 14 January 2010. Retrieved 2010-03-01.
- Carolyn Duffy Marsan (2000-06-26). "'HTTP on steroids' to ease protocol work". Network World. Retrieved 2008-12-18.
- Official website
- Introduction to BEEP at IBM.com. Archived from the original on September 12th, 2011.
- RFC 3080 The Blocks Extensible Exchange Protocol Core
- RFC 3081 Mapping the BEEP Core onto TCP
- RFC 3117 On the Design of Application Protocols, design considerations of the BXXP protocol as told by its creators
|This computer networking article is a stub. You can help Wikipedia by expanding it.|