Quote:
Originally Posted by theducks
erwin
Timing, caching and locking are the biggest banes to a shared network
(this assumes a caseless solution to OS filenames will be implemented)
Any change requires a full lock on (server side) for all affected records AND FILES/Folders
All local caches of data for those must be flushed and Locked, (then refreshed at the end of the change transaction)
BTW the locking system needs to be OS independent  |
I am not sure why you post this, to what question is this an answer? Is this the way calibre is working? Is it transaction based? Does it do file locking? Are you familiar with the code?
It seems even simple file copy/move/rename operations fail if you operate calibre via a network mapped drive letter. That still strikes me as strange.