I wrote:
> > While its not elegant, (a) is just a few seconds work. If your
> > application can stand that, why not?

Minor confusing inducing word use here, I meant to suggest that it takes only
a couple seconds to *implement* a cron job restart mechanism.

* Arturo FM wrote [2006-11-08 18:12:08 +0100]:
> What happens if an user is using a connection in this just moment? Probably
> he/she loose his/her session :(

No -- not if we are talking about a database-backed persistence system for
sessions, which we seem to be assuming based on your discussion.

The unlucky user who happens to hit the restart time dead on will simply get
an indication from their browser that a connection can't be made. Firefox
even puts up a helpful error message which includes:

    Unable to connect

    Firefox can't establish a connection to the server at
    superduperwebapp.com.

    * The site could be temporarily unavailable or too busy. Try again in a
      few moments.

Most folks will hit refresh and carry on.

Remember, http is a stateless environment - the browser doesn't know what to
expect from request to request; and while the server is down momentarily,
"state" won't be changing either, because it can't!