RE: Soap Over Beep Question

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