Blocks Extensible Exchange Protocol (BEEP)
Blocks Extensible Exchange Protocol (BEEP) from IETF defines a connection-oriented Internet protocol. A SOAP mapping for BEEP has been defined. SOAP messages inherit the additional qualities of service from BEEP for maintaining session context at the sender and the receiver. (SOAP itself does not maintain any context.) The context is used to create a connection that relates multiple messages as coming from the same source or intended for the same target. Security and transaction context can also be associated with a connection.
Work on BEEP concluded in March 2002. The IETF is working with the W3C on the XML Protocol (XMLP).
More on the general topic: XML Protocol (XMLP)
Related Online Briefings
- Online Briefing: Change Analysis of Systems Integration Techniques
- Online Briefing: Non-Technical Change Issues Related to SOA
Author: Douglas K Barry
You may use this material for your work or classes. Reprint Policy. Be sure to check the menu at the left for other articles available on this site.
The Savvy Manager's Guide
Douglas K Barry is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.
Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)
by Douglas K Barry with David Dick
This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.