[BEEPwg] Soap Over Beep Question
Fri, 28 Jun 2002 09:59:04 -0700 (PDT)
I think this is a legitimate issue for the SOAP/BEEP RFC.
Message exchange patterns is a hot discussion topic over at the XMLP WG,
and its not clear (at least to me) how the message pattern for a
particular message will be expressed. But no matter what, I would expect
that message patterns for each message type, even on a single BEEP
channel, could be different.
THUS, for a recipient peer to know which message pattern is intended,
there either a) has to be a way to express the desired message pattern at
the "transport" level (e.g. within a BEEP message/channel) or b) within
Thus, the SOAP/BEEP profile will either have to provide a facility for
communicating the intended message exchange pattern (a per-message
header?) or the recipient node will have to at least partially process the
incoming message to decide which messaging pattern is appropriate (and
whether a NUL or RPY response is appropriate).
Either way, it seems that the SOAP/BEEP RFC is inadequate here because it
assumes the recipient has knowledge of the messaging pattern for a
particular message without giving the recipient any chance to figure it
On Fri, 28 Jun 2002, Marshall Rose wrote:
> > Since there is nothing in the syntax of SOAP Over Beep messages
> > which suggests how the message is to be replied with (i.e. if
> > this is a one way, 2 way or multi answer response)..the server
> > will only know about the type of message pattern being used only
> > from processing the SOAP message.
> this is really a soap-specific issue, not a beep- or soap-over-beep issue.
> the answer is the "server" can either have some kind of pre-knowledge over the kind of messages it gets (i.e., the service it offers only dones one-way exchanges), or, the first thing the "server" does is parse the envelope and thereby know what's what.
> there, are, of course, some interesting failure modes with either approach.
> BEEPwg mailing list
Gabe Wachob firstname.lastname@example.org
Founder, WiredObjects http://www.wiredobjects.com