- From: David Orchard <dorchard@bea.com>
- Date: Mon, 15 Sep 2003 11:45:16 -0700
- To: <www-tag@w3.org>
At the end of the draft finding, it says "Section 3 WSDL 1.2 Bindings [WSDL] provides a binding to HTTP GET, which makes it possible to respect the principle of using GET for safe operations. However, to represent safety in a more straightforward manner, it should be a property of operations themselves, not just a feature of bindings.". I'm not quite sure what this means. Does this suggest that there should be a general property of operations that specifies safetey, which could then be bound to POST? That is a operation declarated safe could be bound to POST? I think that's the right interpretation, in which case I'm comfortable with the wording. Interestingly, I just heard the need from 2 customers last week who want to be able to have a "ping" function to test the availability of a service. At this point, I don't think the WSDL WG has accepted this requirement. The editors copy of the requirements document (last updated feb 2003), has requirement R125 as the only TAG sourced requirement. "R125 The normative description of the InterfaceBinding for SOAP 1.2 MUST support the SOAP 1.2 MEP for HTTP GET in and HTTP SOAP out. (From TAG. Last discussed 26 Sep 2002.) " I propose to ask them for some clarification and call the finding to their attention. Cheers, Dave
Received on Monday, 15 September 2003 14:48:37 UTC