(a prerequisite would be to have per-collection sync intervals.)
Then you could respect http header meta-information, e.g. when it tells you how long this resource may be cached or when its expiring (and then trigger a new sync).
This could help save bandwith and computing time on the long run if servers send correct headers.
It seems the HttpComponents used by DAVdroid don’t provide a persistent cookie store. The BasicCookieStore (which will be used when the .disableCookieManagement is removed) is only an in-memory list of cookies. This would suffice to make a sync process one “session” and still won’t have the complexity of a persistent cookie store, so I’ll enable it.
