remote discovery phase on client startup

[moscicki]

What is the reason to do the remote discovery (PROPFIND on all directories) on client startup?

If I go offline without restarting the client I am also exposed to potentially large number of changes on the server when I come back online -- and there is no remote discovery -- because the ETAG propagation works well on the server.

If for operational reasons it is required to rescan the server by the clients I think one should have a server-side mechanism to force all or selected clients to do so (well, in that case not all clients at exactly the same time, of course).

[guruz]

I'm not sure I understand.
If there were no remote changes, it should do exactly 1 PROPFIND on /. It will then see in its local .csync_journal.db that the server Etags didn't change.
This is independant from client startup.

[moscicki]

OK, it may be that I am running in circles here. Sorry guys, too much testing ;-) I think I was mislead by the "discovering" message which actually discovers the local files not the remote ones (which is a problem in itself -> #2297).