Re: How to monitor long-running fork in Skunkweb?

--- [email protected] wrote:
> On Wed, Mar 09, 2005 at 08:18:10AM -0800, Drew Csillag wrote:
> > But single writer, mulitple readers should always be ok right
> now...
> 
> Ah.  This is my case.  I will have a long-running process
> periodically
> update it's status into the session, while a monitor periodically
> reads that status and displays it to the user.  I am interested to
> read the concurrency discussion.

With either the FSSession store or a SQL based version, single-writer
multiple reader should always be ok.  

Also, I've thought a bit more about converting FSSession store to a
write-temp-rename scenario and decided against it if we want an
atomic update function.  The combination of file locking and wtr
probably won't work too well.

Drew


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more. 
http://info.mail.yahoo.com/mail_250


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click