Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
RFC 4227
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol … Received changes through RFC Editor sync (changed abstract to 'This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding describes how SOAP messages are transmitted in the network. The SOAP is an XML-based (eXtensible Markup Language) messaging protocol used to implement a wide variety of distributed messaging models. It defines a message format and describes a variety of message patterns, including, but not limited to, Remote Procedure Calling (RPC), asynchronous event notification, unacknowledged messages, and forwarding via SOAP intermediaries. [STANDARDS-TRACK]') |
|
2017-05-16
|
(System) | Changed document authors from "Marshall Rose" to "Marshall Rose, Eamon O'Tuathail" |
|
2015-10-14
|
(System) | Notify list changed from mrose@dbc.mtview.ca.us, eamon.otuathail@clipcode.com to eamon.otuathail@clipcode.com |
|
2006-01-10
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2006-01-10
|
Amy Vezza | [Note]: 'RFC 4227' added by Amy Vezza |
|
2006-01-09
|
(System) | RFC published |