On Fri, 2008-10-31 at 10:10 -0600, Alex Rousskov wrote:
> Does anybody know why DeferredReadManager destructor forces deferred > reads to read by calling flushReads? Besides leading to bugs, it seems > kind of pointless to try to read if the object that guarded deferred > reads is being destructed anyway. Its what the old code it replaced did. -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
