BEEP
Click on the red underlined text to get to the source
... SOAP 1.1 envelopes[1] are transmitted using a
BEEP profile[2]. In the W3C, the XMLP effort is evolving SOAP ...
... one-to-one", and "one-to-many" are
used in the context of BEEP. In particular, Sections 2.1 and 2.1.1
of [2] discuss BEEP ...
... BEEP Profile Identification ...
...
The BEEP profile for SOAP is identified as
...
...
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 ...
... END
In addition, the BEEP profile for SOAP also allows envelopes to be
transmitted as the root ...
... a "Content-ID:" header. However, because BEEP provides an 8bit-wide
path, a "transformative" Content-Transfer-Encoding ...
... 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,
...
... RPY" message containing an envelope.
Finally, the BEEP profile for SOAP does not use the "ERR" message for
...
... 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 ...
... 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 5.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 [2] for an example of how a BEEP ...
... BEEP peers issue a new greeting. Consult
Section 3 of [2] 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 7.4.
...