You could set a property in the context scope that flags the 'maintenance page' or something. To detect the flag, you could use a filter to redirect the user to the maintenance page, or have your base Action class look for the flag and react accordingly.
Ideally, you'd do this from some form of admin page. On Tue, 07 Sep 2004 13:26:10 -0400, Dean A. Hoover <[EMAIL PROTECTED]> wrote: > I have a website I'm working on that is > fairly typical (I think): there areoperations that > anyone can do and operations that require > a user to be logged in. Authorization and > authentication are done using a database. > From time to time, the site needs to be > shutdown for general maintenance, upgrades, > etc. > > I want to give the users fair warning that the > site will be shut down at such and such a > time. I also want to prevent the users from > performing operations during this "shutdown". > I think it would be good if there were still > a home page up, with indications that the > system is offline and should be back by a certain > time. At first I thought I would create some > table in my database to control some of this > but I think this is not such a great idea, as the > reason for taking the site down may be to do > something radical to the database. > > Is there some "best practice" for accomplishing > this? > > Thanks. > Dean Hoover > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
