[Speedycgi-users] what happens when...

[Dan G. <spe...@go...>]

Hi all,
I'm new to speedycgi, but I already love it.  Thanks Sam!

I'm trying to understand a few things, and I'm hoping someone
on the list can help me.  In my past lives dealing with cgi
and mod_perl, I remember your code might get a sigpipe or
somesuch from apache in some cases, such as when the user
behind the browser hit the escape key.

When using speedy, are any of these signals passed along to
the persistent perl program?  Is this different when using
the speedy front-end versus the mod_speedy front-end?  Will
the back-end ever be in a situation where it's writing to the
front-end via a socket and the front-end reader goes away? 
Do I need to equip my perl code with signal handlers for
this possibility or is it hidden from my perl code?

Secondly, is there a graceful way to get the speedy backends
to exit?  Ideally, I'd like to be able to have the perl
code tell the backend "Hey, I'm done - no really, stop,
I don't want to run again... No, I mean it. Quit already."
With exit and die now meaning 'wait for the next request
and start from the top', how do you _really_ exit?

Thanks a lot!!!
-Dan