Re: [phpesp-dev] soma changes

[Bishop B. <ph...@id...>]

Quoting Franky Van Liedekerke <lie...@te...>:

> I can add the same logic to the survey side if wanted. But what do you
> normally do when updating? Maybe we should just have a file called
> "disabled" or so, and as long as that file is there, all surveys appear
> offline (something like "The system is undergoing an update, please be
> patient"). What do you think?

This is an important issue in my particular case, as at any given time  
there can be up to 30,000 unique people hitting the surveys at one  
time. In my situation, I tell Apache to redirect to a maintenance  
page, then run the update from the command line using a script that  
was previously tested on a QA server.  Usually the update implies only  
a few seconds of down-time, which is great.  Whatever process is  
chosen, it must be atomic, so create a lock file, flock() it, and run  
the update.  Might need a method to force the lock file too, just in  
case something dies (server boot)?

bishop

-- 
Bishop Bettini
ideacode, Inc.
(main) +1 919 341 5170 / (fax) +1 919 521 4100

Visit us on the web at:
ideacode.com          Professional software research and development
reviewmysoftware.com  Improve sales! Review your software before you release
bytejar.com           Solutions to those annoying development problems