-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/08/13 06:06, Ralf Ramsauer wrote: > Neither cifs.
I worked on a CIFS server (visionfs)[1]. They are a convoluted complicated mess. During the OLE2 era, Microsoft's apps abused locking as a means of inter-process communication. It got very complicated, with Excel especially bad/adventurous in this respect. CIFS locks are also completely different in virtually every way from Unix ones. You cannot map between them sensibly. Both VisionFS and Samba ended up having a "database" of the lock information and essentially ignored what Unix said. What this means is you cannot use CIFS from a Unix box and get correct semantics because the Unix API does not expose anything close to cifs reality. Windows machines can in theory do the right thing. It has been a while, but back in those days there would be calls over the wire that I couldn't find any API to request. For well over a decade the protocol has roughly consisted of NT kernel data structures being sent over the wire. The server side gets adjusted to detect and work around bugs in the various client versions. Because of the asynchronous nature of networked file systems, race conditions, and the possibilities of running out of disk space, most apps have done updates by writing to a new file and only when everything is successful overwriting the original. Updating a (possibly shared) file in-place which is what SQLite does is fraught with peril, which is why it turns out to be the least exercised part of protocols and where bugs/quirks lie. [1] http://www.rogerbinns.com/visionfs.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlIMB3wACgkQmOOfHg372QTyGgCgxB/7XxUibw+p0T/aI0cNecE4 ZegAoMDoh7RKb6hZmXsWTbreWhXpSYWP =0UbL -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users