Re: WebDAV sync report w/invalid sync token

Werner DonnĂ© <[email protected]> Tue, 15 Nov 2011 15:03:11 +0100
Newsgroups gmane.ietf.webdav
Message-ID <CA+uXuOXz12g4osavdUKihUwTGMfJY1LEKkN+L=_07EN7cNefsg@mail.gmail.com>
--000e0cd567ee9e4b6d04b1c67227
Content-Type: text/plain; charset=ISO-8859-1

Hi Ken,

Your conclusion is correct, because the draft uses the REPORT method, which
is specified in RFC 3253. However, the draft doesn't refer to this RFC.
This would probably be difficult, because synchronization is supposed to
work as well for servers and clients that don't implement RFC 3253. Some
day the generic stuff in RFC 3253 should move to a separate RFC or perhaps
RFC 4918.

Best regards,

Werner.

On Tue, Nov 15, 2011 at 2:32 PM, Ken Murchison <[email protected]> wrote:

> Folks,
>
> What is the proper response code for a sync-collection report if the
> sync-token is either invalid or out of date?  The I-D doesn't seem to
> specify, so looking at RFC 3253 section 1.6 it appears that 403 and 409 are
> the two options for a precondition failure, with 409 presumably being the
> correct choice in this case.  Am I missing something?
>
> Thanks,
> Ken
>
> --
> Kenneth Murchison
> Principal Systems Software Engineer
> Carnegie Mellon University
>
>


-- 
http://www.pincette.biz/
Handling your documents with care, wherever you are.

--000e0cd567ee9e4b6d04b1c67227
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Ken,<div><br></div><div>Your conclusion is correct, because the draft us=
es the REPORT method, which is specified in RFC 3253. However, the draft do=
esn&#39;t refer to this RFC. This would probably be difficult, because sync=
hronization is supposed to work as well for servers and clients that don&#3=
9;t implement RFC 3253. Some day the generic stuff in RFC 3253 should move =
to a separate RFC or perhaps RFC 4918.</div>
<div><br></div><div>Best regards,</div><div><br></div><div>Werner.<br><br><=
div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 2:32 PM, Ken Murchison <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]">[email protected]=
u.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Folks,<br>
<br>
What is the proper response code for a sync-collection report if the sync-t=
oken is either invalid or out of date? =A0The I-D doesn&#39;t seem to speci=
fy, so looking at RFC 3253 section 1.6 it appears that 403 and 409 are the =
two options for a precondition failure, with 409 presumably being the corre=
ct choice in this case. =A0Am I missing something?<br>

<br>
Thanks,<br>
Ken<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
-- <br>
Kenneth Murchison<br>
Principal Systems Software Engineer<br>
Carnegie Mellon University<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><a href=3D"http://www.pincette.biz/">http://www.pincette.biz/</a><br>Hand=
ling your documents with care, wherever you are.<br><br>
</div>

--000e0cd567ee9e4b6d04b1c67227--