[caldeveloper-l] sync-tokens vs PROPFIND

[David Given]

Hello everybody,

I have an RFC question I'd appreciate some feedback on...

We have a situation where a Calendar client is trying to get the etags of
every event in an enormous calendar in a single query. Naturally, this
isn't working.

They're doing this:

PROPFIND /caldav/v2/$USERNAME/events
<?xml version="1.0" encoding="UTF-8"?>
<A:propfind xmlns:A="DAV:">
  <A:prop>
    <A:getcontenttype/>
    <A:getetag/>
  </A:prop>
</A:propfind>

As you can see, they're not asking for a sync token.

RFC6578 section 3.6 provides a mechanism where clients can ask for
paginated responses, where the server returns partial data with a 507
status code, and a new sync token so they can continue the query. It is a,
however, a bit ambiguous as to whether this is supported for methods other
than REPORT. The interwebs suggest it is (but I'd appreciate a
clarification here).

My question is. however:

Is it permissable to return a sync-token (and expect the client to honour
it) *even if the client's original query didn't ask for it*?

I'm hoping the answer is going to be yes, but if it's no --- any
suggestions?

Thanks!

David Given
dtrg at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20171107/350f5bae/attachment.html>