All, The proposal is as follows, 1/ add a paragraph to explain what 'safe' and 'idempotent' means, and the impact on operations (like being able to redo a request when there is a failure at the underlying protocol level, or using a timeout when that information is not available, like UDP packets). The text might reference http://tools.ietf.org/html/rfc2616#section-9.1 directly or even http://tools.ietf.org/html/draft-ietf-httpbis-method-registrations-01 or we can come up with our own definitions if needed (that is the main point of discussion I guess). 2/ for each resource operation, add a small table with the safeness and idempotent properties (and this table would also act as a short summary for each paragrahp, so include the values of /s:Envelope/s:Header/wsa:Action, for example). [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533 -- Baroula que barouleras, au tiéu toujou t'entourneras. ~~YvesReceived on Tuesday, 3 March 2009 13:32:25 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 3 April 2009 01:27:37 GMT