- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 17 Oct 2001 14:32:28 -0700
- To: XML Distributed Applications List <xml-dist-app@w3.org>
I think this may have been covered before; if so, a pointer to the discussion (which I couldn't find) would be appreciated. Our definition of node is: A SOAP node processes a SOAP message according to the formal set of conventions defined by SOAP. The SOAP node is responsible for enforcing the rules that govern the exchange of SOAP messages and accesses the services provided by the underlying protocols through SOAP bindings. Non-compliance with SOAP conventions can cause a SOAP node to generate a SOAP fault (see also SOAP receiver and SOAP sender). Here, I infer that 'processes a SOAP message according to the formal set of conventions defined by SOAP' refers to the processing model in 2.5, "Processing SOAP Messages." Our definition of initial sender is: The SOAP sender that originates a SOAP message as the starting point of a SOAP message path. And a SOAP sender is defined as a SOAP node. Following these definitions, with the above interpretation of the processing model, it appears that initial senders follow the processing model. Is this the case? My intuition is that our definition of node is based on the incorrect criteria. I can see cases where it would be useful to target blocks at the initial sender (e.g., 'encrypt the body and insert a decryption block targeted at foo'), but I don't remember seeing evidence of this in our discussions of how modules work, etc. (tho my memory is notoriously bad). -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 17 October 2001 17:32:29 UTC