On Tue, June 20, 2006 12:53 pm, Ben Liu wrote: > I'm not sure this is strictly a PHP related question or perhaps a > server admin question as well. What do you do when you are trying to > shutdown a web application for maintenance (like a membership or > registration-required system)? I understand that you can temporarily > upload or activate a holding page that prevents users from continuing > to login/use the system, but how can you insure that there are no > ongoing sessions or users still in the process of doing something? > What's the best method for handling this, especially if you don't have > full control of the server hosting the web app? It's too late for this go-around, but... If it's something you really want to "do right" and it's mission-critical and you have a ton of time... You *could* tag every user/record/session with a "version" number, and then you *could* check what version they are currently "on" and then "do the right thing" for them in that version. Obviously, this could get very complicated, very very very fast... Or, perhaps not. Perhaps you'd have a special dir set up for each "old" version, and if they submitted a page under the "old" version in their session, you'd just include stuff from that old version directory, by munging include_path() to use old code and not new code. Then, when they logout, and get a new session later, "poof" they are now in the "new" version. This is obviously not a TRIVIAL solution, but it's at least feasible if this problem truly must be solved rather than ignored. :-) "Crude, but effective Captain" -- Spock _Bearskins and Knives_ -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
