On Tue, 2002-05-14 at 14:23, Aaron Smuts wrote: > Hmmn. I think it has always been a bit funny.
=] All the old stuff is still under the stratum repository, in the Attic. > We may have to update the item in purgatory as not spoolable, then remove it > so the element in the queue will no longer be sppolable. I'm changing 'remove' so that it gets the element and sets it to be not spoolable. > What if it is writing at that moment? I think we need to be able to synchronize remove and put. We could share a lock with the event queue. Basically in remove we would say 'finish whatever the current event is and then pause' to the queue, execute the removal, and the resume the queue. I think that is the only safe way to synchronize the two. Shouldn't be that hard! > Perhaps the put event should get the item from purgatory prior to writing to > disk. > > So on put we put into a purgatory wrapper and then create a put event. > > When the put event runs it could get the item from purgatory first, make > sure it is spoolable and then put. Doesn't it already do this? > On remove we remove from purgatory and disk. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
