SOAP
Click on the red underlined text to get to the source
... version 1.2 [15] and MAY support other versions, such as SOAP version
1.1 [17]. This memo specifies how SOAP ...
... SOAP version
1.1 [17]. This memo specifies how SOAP envelopes [15] are
transmitted using a BEEP profile ...
... senders and receivers. For example, when
referring to SOAP version 1.2, the term "envelope" refers to the
"Envelope" element ...
... envelopes [17]. If an implementation of this memo chooses to
implement SOAP version 1.1, then it should support both this Uniform
Resource Identifier (URI ...
...
There are two states in the BEEP profile for SOAP, "boot" and
"ready":
...
...
o In the "ready" state, either peer begins a SOAP message pattern by
sending a "MSG" message containing an envelope. The other peer
completes the message pattern either by
...
... channel bound to the BEEP profile
for SOAP provides access to a single resource (a network data
object or service ...
...
feature negotiation: if new features of SOAP (such as compression)
emerge, their use can be negotiated.
...
... feature tokens, each indicating an optional feature of the BEEP
profile for SOAP that is being requested for possible use over the
channel.
...
... SOAP Message Packages ...
...
The BEEP profile for SOAP transmits envelopes encoded as UTF-8 and
SHOULD use the media type ...
...
In addition, an implementation of the BEEP profile for SOAP MAY
support transmission of envelopes using the MTOM [7 ...
... startinfo="application/soap+xml; action=
Content-Description: A SOAP message with my pic and sig in it
--MIME ...
... XOP may be used with diverse packaging mechanisms. When
an implementation of BEEP in SOAP does support MTOM/XOP, it SHOULD
support the MIME ...
... BEEP (e.g., sending the attachments on a
different channel to the SOAP channel, which would avoid searching
for the MIME boundary tags and allows lazy delivery ...
... SOAP Message Patterns ...
...
The BEEP profile for SOAP achieves this using a one-to-many exchange,
in which the client sends a "MSG" message containing an envelope, and
...
...
The BEEP profile for SOAP achieves this using a one-to-many exchange,
in which the client sends a "MSG" message containing an envelope, and
...
... BEEP profile for SOAP does not use the "ERR" message for SOAP
faults. When performing one-to-one exchanges, whatever SOAP ...
... SOAP
faults. When performing one-to-one exchanges, whatever SOAP response
(including SOAP faults) generated by the server ...
... one-to-one exchanges, whatever SOAP response
(including SOAP faults) generated by the server is always returned in
the "RPY ...
... the "RPY" message. When performing one-to-many exchanges, whatever
SOAP response (including SOAP faults) generated by the server is
...
... RPY" message. When performing one-to-many exchanges, whatever
SOAP response (including SOAP faults) generated by the server is
always returned in the "ANS ...
...
If there is an error with the BEEP message unrelated to the SOAP
envelope (e.g., poorly formed MIME message or MIME Content ...
... Supported SOAP Message Exchange Patterns ...
...
An implementation of this binding MUST support the following SOAP
Message Exchange Pattern (MEP):
...
... binding instances conforming to this specification:
o A SOAP node instantiated at the BEEP peer that initiates the
message exchange ...
... Behavior of Requesting SOAP Node ...
...
The overall flow of the behavior of a requesting SOAP node follows a
state machine description consistent with Section 6.2 of [3 ...
... In order to avoid deadlock during streaming (see Section 6.2.3 of
[3]), the requesting SOAP node MUST be able to process incoming SOAP
response information while the SOAP ...
... [3]), the requesting SOAP node MUST be able to process incoming SOAP
response information while the SOAP request is still being
...
... SOAP node MUST be able to process incoming SOAP
response information while the SOAP request is still being
transmitted.
...
... response message are completed. The
response message is assumed to contain a SOAP envelope serialized
according to the rules for carrying SOAP messages in the media type ...
... response message is assumed to contain a SOAP envelope serialized
according to the rules for carrying SOAP messages in the media type
given in the Content-Type ...
... Behavior of Responding SOAP Node ...
...
The overall flow of the behavior of a responding SOAP node follows a
state machine description consistent with Section 6.2 of [3 ...
... soap.beep" and "soap.beeps",
which identify the use of SOAP over BEEP over TCP. Note that, at
present, a "generic" URL scheme ...
... that prior to starting the BEEP profile for SOAP, the BEEP session
must be tuned for privacy ...
... SOAP Profile Feature Registration Template ...
...
When a feature for the BEEP profile for SOAP is registered, the
following information is supplied:
...
... Registration: The SOAP Profile ...
... Messages starting one-to-one exchanges: bootmsg, a SOAP "envelope"
Messages in positive replies: bootrpy, a SOAP ...
... SOAP "envelope"
Messages in positive replies: bootrpy, a SOAP "envelope"
Messages in negative replies: error
Messages ...
...
Messages in negative replies: error
Messages in one-to-many exchanges: a SOAP "envelope"
Message Syntax: a SOAP ...
... Semantics: corresponds to the relevant SOAP specification,
e.g., for SOAP version 1.2, cf. [2].
...
... 10]
Intended usage: identifies a SOAP resource made available using the
BEEP profile for SOAP ...
... SOAP resource made available using the
BEEP profile for SOAP
Applications using this scheme: cf. "Intended usage", above
...
... 10]
Intended usage: identifies a SOAP resource made available using the
BEEP profile for SOAP ...
... SOAP resource made available using the
BEEP profile for SOAP after the BEEP session has been tuned for
privacy ...
...
The IANA has also registered "SOAP over BEEP" as a TCP port number,
as specified in Section 8.4.
...
...
Finally, the IANA maintains a list of SOAP profile features, cf.
Section 7.1. The IESG is responsible for assigning a designated
expert ...
... IANA making the
assignment. Prior to contacting the IESG, developers of SOAP profile
features must use the mailing list beepwg@lists.beepcore.org to
...
... Nielsen, H., Mendelsohn, N., Gudgin, M., Hadley, M., and J. Moreau, "SOAP Version 1.2 Part 1: Messaging Framework", W3C ...
... Nielsen, H., Hadley, M., Moreau, J., Mendelsohn, N., and M. Gudgin, "SOAP Version 1.2 Part 2: Adjuncts", W3C REC REC- soap12-part2-20030624, June 2003. ...
... Nottingham, M., Mendelsohn, N., Gudgin, M., and H. Ruellan, "SOAP Message Transmission Optimization Mechanism", W3C REC REC-soap12-mtom-20050125, January 2005. ...
... Mitra, N., "SOAP Version 1.2 Part 0: Primer", W3C REC REC- soap12-part0-20030624, June 2003. ...
... O'Tuathail, E. and M. Rose, "Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)", RFC 3288(-> 4227prop) ...
... Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H., Thatte, S., and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", W3C NOTE NOTE-SOAP-20000508, May 2000. ...
... Barton, J., Thatte, S., and H. Nielsen, "SOAP Messages with Attachments", W3C NOTE NOTE-SOAP-attachments-20001211, December 2000. ...
... Barton, J., Thatte, S., and H. Nielsen, "SOAP Messages with Attachments", W3C NOTE NOTE-SOAP-attachments-20001211, December 2000. ...
... Appendix A. SOAP with Attachments (Informative) ...
... 3288(-> 4227prop) [16], a BEEP profile for SOAP
MAY allow envelopes to be transmitted as the root part of a
...