RE: Soap Over Beep Question

Gabe Wachob <[email protected]> Sun, 30 Jun 2002 12:02:59 -0700 (PDT)
Newsgroups gmane.ietf.beep
Message-ID <[email protected]>
This discussion of where to put message exchange pattern information is a
live topic over at the XMLP, from what I can tell.

Some there appear to take the position that the MEP should be expressed
*by the transport binding* - that is, it would be expressed within the
BEEP profile (perhaps as a custom message header?). They apparently
believe that *they* are going to specify or have great influence over the
SOAP bindings.

So, your conclusion about where to put that information *may* end up being
in direct contradiction to what the XMLP group says.

Its not clear to me at this point, however, where the prevailing winds are
blowing, and I'm not sure this issue is soon to be closed (or if it has
very recently been closed at all).

	-Gabe

On Sun, 30 Jun 2002, Eamon O'Tuathail wrote:

> Rohit,
>
> We did look at where to put information that is exchanged between the
> BEEP peers, and concluded it was best to put it all inside the SOAP
> envelope, and not to have any additional information flows (external to
> the envelope).
>
> Note that RFC 3288 focuses on how SOAP travels over BEEP, not on the
> internals of the SOAP envelope - the latter is the job of the W3C
> XMLP/SOAP WG.
>
> I can appreciate why people might like an explicit description of the
> message pattern to use, but you have to ask yourself would such a
> description be useful only to BEEP, or might it also interest non-BEEP
> SOAP users too (e.g. those who use SOAP-over-HTTP or SOAP-over-SMTP). I
> think you will answer "yes" to this, and therefore the message pattern
> description should rightly be placed inside the SOAP envelope (as a SOAP
> message header), so it can be used by all.
>
> At the moment there is no (IANA-like) registry of possible message
> pattern descriptions, but I could see it envolving in future. For now,
> peers that accept multiple message patterns must determine from the
> message how to respond.
>
> Eamon
>
> _______________________________________________
> BEEPwg mailing list
> [email protected]
> http://lists.beepcore.org/mailman/listinfo/beepwg
>

-- 
Gabe Wachob                       [email protected]
Personal                       http://www.wachob.com
Founder, WiredObjects    http://www.wiredobjects.com