On 12/15/18, Pierre Tempel <pierretem...@gmail.com> wrote: > > Hm. Doesn't this mean the proposed solution still works, but with > directories instead of files for the sake of atomicity? I.e. for each > lock type, create a unique dir name (e.g. ".1.lock") and stat for all > lock types when changing levels?
I think you probably need a counter in order to implement a reader/writer lock, don't you? We used to do a stocastic simulation reader/writer locks on win98 by using 512 separate locking bytes. But is seems a little excessive to have 512 separate locking directories. Does anybody else know how to implement reader/writer locks using lock files? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
