BEEP
Click on the red underlined text to get to the source
... SOAP envelopes [15] are transmitted using a
BEEP profile [1]. Conforming implementations MUST support SOAP
...
... SOAP envelopes [15] are
transmitted using a BEEP profile [1]. Unlike its predecessor,
RFC3288(-> 4227prop) ...
... one-to-one", and "one-to-many" are
used in the context of BEEP. In particular, Sections 2.1 and 2.1.1
of [1] discuss BEEP ...
... BEEP Profile Identification ...
...
The BEEP profile for SOAP is identified as
...
... "http://iana.org/beep/soap/1.1".
In BEEP, when the first channel is successfully created, the
...
...
resource identification: each channel bound to the BEEP profile
for SOAP provides access to a single resource (a network ...
... o the "features" attribute, which, if present, contains one or more
feature tokens, each indicating an optional feature of the BEEP
profile for SOAP that is being requested for possible use over the
channel ...
... 6].
In addition, an implementation of the BEEP profile for SOAP MAY
support transmission of envelopes using the MTOM ...
... 8] for guidance on MIME Multipart/Related
usage. Because BEEP provides an 8-bit-wide path, a "transformative"
Content-Transfer-Encoding ...
... 8], XOP may be used with diverse packaging mechanisms. When
an implementation of BEEP in SOAP does support MTOM/XOP, it SHOULD
...
... support others. Additional formats could, in the future, include XOP
package formats specific to BEEP (e.g., sending the attachments on a
different channel to the SOAP channel ...
... being returned.
The BEEP profile for SOAP achieves this using a one-to-many exchange,
in which the client ...
... in a response being returned.
The BEEP profile for SOAP achieves this using a one-to-one exchange,
...
... results in zero or more responses being returned.
The BEEP profile for SOAP achieves this using a one-to-many exchange,
in which the client ...
... ANS" messages.
If there is an error with the BEEP message unrelated to the SOAP
envelope (e.g., poorly formed MIME message ...
...
o A SOAP node instantiated at the BEEP peer that initiates the
message exchange may assume the role ...
...
o A SOAP node instantiated at the other BEEP peer may assume the
role (i.e., the property http://www.w3.org/2003/05/soap/
...
...
In the "Init" state, a BEEP message is formulated according to
Section 3, transmission of the message begins, and then the state
changes to "Requesting".
...
... and the arrival of the response is awaited. When the beginning of
the response message is received, if it is a BEEP ERR message, then
the state ...
... soap.beep" and "soap.beeps",
which identify the use of SOAP over BEEP over TCP. Note that, at
present, a "generic" URL scheme ...
... The "soap.beep" URL scheme indicates the use of the BEEP profile for
SOAP running over TCP/IP ...
... URL scheme specified in Section 6.1, with the exception
that prior to starting the BEEP profile for SOAP, the BEEP session
...
... starting the BEEP profile for SOAP, the BEEP session
must be tuned for privacy. In particular, note that both URL schemes ...
...
There are two ways to perform privacy tuning on a BEEP session,
either
...
... Regardless, upon completion of the negotiation process, a tuning
reset occurs in which both BEEP peers issue a new greeting. Consult
Section 3 of [1] for an example of how a BEEP ...
... BEEP peers issue a new greeting. Consult
Section 3 of [1] for an example of how a BEEP peer may choose to
issue different greetings based on whether privacy is in use.
...
...
When a feature for the BEEP profile for SOAP is registered, the
following information is supplied:
...
... Intended usage: identifies a SOAP resource made available using the
BEEP profile for SOAP after the BEEP session has been tuned for
...
...
The IANA has also registered "SOAP over BEEP" as a TCP port number,
as specified in Section 8.4.
...
... IANA now broadens these three registries to support the family of
BEEP profiles defined by this URI prefix ...
... URL
prefix is defined to support a family of BEEP profiles corresponding
to different versions ...
... Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)", RFC 3288(-> 4227prop), June 2002. ...
... compatibility with RFC3288(-> 4227prop) [16], a BEEP profile for SOAP
MAY allow envelopes to be transmitted as the root ...
... contain a "Content-ID:" header. However, because BEEP provides an
8bit-wide path, a "transformative" Content-Transfer-Encoding ...