httpd-modules-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Meyer <mwm-keyword-apache.b9a...@mired.org>
Subject Re: Doing left-over request processing at startup....
Date Wed, 29 Dec 2010 14:21:44 GMT
On Wed, 29 Dec 2010 08:27:33 -0500
Jerry Stuckle <jerry@smartechhomes.com> wrote:

> 
> 
> On 12/29/2010 7:07 AM, Mike Meyer wrote:
> > On Wed, 29 Dec 2010 11:00:09 +0200
> > Issac Goldstand<margol@beamartyr.net>  wrote:
> >
> >> On 29/12/2010 10:52, Mike Meyer wrote:
> >>> The current code actually works fine - except for this timing
> >>> issue. If I kill apache in the middle of handling a reversal, and
> >>> restart it, the first connection will cause the unfinished reversal to
> >>> be finished. I'm trying to find some way to make this happen at
> >>> startup, instead of on the first connection.
> >> Maybe try something simpler?  Write a script which fires at apache
> >> startup and just makes a dummy request to trigger the queue?  I know
> >> that's a lot less fun and less elegant ;), but will it get the job done?
> >
> > Yeah, I'd been thinking about something like that. Start it a bit
> > after apache, probe the port, connect, count to one, and go away....
> 
> If you don't need to give feedback to the web user, just place the 
> request in a queue, i.e. in a database.  Then start a cron job every 5 
> minutes (or whenever) to process any work in the queue.  Much simpler.

We do need to give feedback to the web user. In fact, failure to do
that means the request has failed, and has to be reversed. That we
need to complete these actions even if apache is rebooted while we're
trying is the root cause of the problem.

       Thanks,
       <mike
-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.

O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

Mime
View raw message