MEP provides an abstraction layer to decouple a SOAP application from the SOAP bindings. An application designed to expect a certain MEP should work equally well with either of the follwing two SOAP bindings: 1. Binding has native support for the MEP (e.g., HTTP request-response), or 2. Binding has no native support for the MEP, but an abstract SOAP "feature" can be implemented to effectively provide the MEP behavior over the available binding. This allows flexibility to replace underlying bindings (and otherwise configure SOAP processors) without impact to the SOAP applications. I'm not sure how to work this into the WSA text, but I wanted to capture this aspect of MEPs. PaulReceived on Monday, 26 January 2004 16:22:38 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:25 GMT