https://bz.apache.org/bugzilla/show_bug.cgi?id=66313
--- Comment #4 from m...@netbsd.org --- (In reply to Christophe JAILLET from comment #3) > maybe see also > https://bz.apache.org/bugzilla/attachment.cgi?id=21173&action=edit in bug > 36636. There may be some gains here, but I am a bit skeptical. If many clients share a read access to DAVLockDB, locking a file on the DAV fs will still wait for a while to get an exclusive access. We could get a real breakthrough by having a dedicated thread/worker opening DAVLockDB, and processing operations on behalf of ordinary thread/workers. That would completely eliminate lock contention. But I do not know hos easily such a service could fit in Apache, with the different server models supported. Hints welcome. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
