It appears that: ucb/source/ucp/webdav-curl/SerfLockStore.cxx Hasa thread that wakes up 25 times per second: std::this_thread::sleep_for( std::chrono::milliseconds(1000/25) ); to see if some timeouts have expired. However - the method 'refreshLocks' could easily tell us how long it will be until we need to refresh another lock; and if we wait/sleep on a condition we can signal that if new ones are added. This would make scheduling far more relaxed. Suggest adding a shortest deadline in milliseconds to wake up again as a return value from 'refreshLocks()' there and sleeping that long. =)
Hi Michael; not sure if you're interested in this one =) but was a curio I stumbled over in some code reading there.