Certainly sounds better than my theory, that's for sure. :)
> Nah.
>
> For each Listen ip:port as configured in httpd.conf,
> the parent Apache process bind()s a socket to that ip and port
> and hangs a listen() on it. As many as you have specified.
>
> Whenever a request comes in on a <ip,port> it is farmed off to
> a child task to process, and another bind()/listen() is done
> to listen for the next incoming request on THAT IP AND PORT.
>
> If you've done any pre-forking/multi-ip-port server code, the above
> methodology will be familiar. For those who want to learn more,
> there are some excellenet chapters on this very topic in
> "The Perl Cookbook", towards the end of the book.
>
> So all I really want is a preforking multi-IP highly configurable
> POP-3 server that functions basically the same way that Apache
> does.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
