On 25/09/14 17:26, Jakub Moscicki wrote:
This is to let you know what we do certain migration situations when the etags on the server are lost or scrambled. I would like to know if anyone is having a similar practice or if client developers see any problem with that (and are aware that we use this as a feature of the system).
That said, I think the server storage backends should create more predictable ETags. For a normal filesystem backend, this could be something like a hash(inode + filesystemid + size + mtime).
That way such situations (I heard of people uninstalling and re-installing the oC server to upgrade) are better handled without any intervention needed on the sync client machines.
_______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
