- From: Werner Donné <werner.donne@pincette.biz>
- Date: Tue, 19 Apr 2011 16:25:08 +0200
- To: Cyrus Daboo <cyrus@daboo.name>
- Cc: Arnaud Quillaud <arnaud.quillaud@oracle.com>, w3c-dist-auth@w3.org
Hi Cyrus, On 19 Apr 2011, at 16:08, Cyrus Daboo wrote: >> What is the rationale behind sending it only once? > > Same rationale that causes changes to a resource to only be reported once. Basically a server only sends notification of a change in "state" of a resource once to anyone particular client for the simple reason that sync clients are expected to persist some state from the last sync operation. > > Simply put a "405" resource is no different from any other, except as follows: > > - When the resource first appears in the sync set, it is reported with a 403+DAV:error code > - No change notifications are sent for the resource since it does not report any changes > - If the resource is removed, a 404 is returned > > With that behavior, the "405" is effectively sent only once. > > -- > Cyrus Daboo I see what you mean now. Thank you. Werner. -- http://www.pincette.biz/ Handling your documents with care, wherever you are.
Received on Tuesday, 19 April 2011 14:25:42 UTC