On Fri, Jun 12, 2009 at 12:41 AM, Sean Conners...@conman.org wrote:
It was thus said that the Great Vinay Nagrik once stated:
Thank you Andrew and Tom,
Thank you for your insightful replies. These have definitely helped me in
understanding the major issues.
At this moment I can not
The parent process then takes the connection socket, and passes it on to
an available child process to handle---once the socket is passed on to the
child (and no, the three-way TCP handshake does not have to happen again,
the connected socket is passed from the parent to the child process),
Great, Great, Great! Sean Conner and Andrew Warnier. This topic is covered
in full without anybody being sarcastic, as is often the case in other
usenet groups.
My heartful thanks to participating parties.
Thanks a lot.
Nagrik
On Fri, Jun 12, 2009 at 12:41 AM, Sean Conner s...@conman.org
Thank you Andrew and Tom,
Thank you for your insightful replies. These have definitely helped me in
understanding the major issues.
At this moment I can not understand How a 'Connecton' is passed from parent
process to child process.
My understanding is
a connection is a combination of (IP
Dear Group,
How do web servers achieve scalability is bothering me for a long time. My
understanding is that an application can open one and only one socket
connection through four system calls (socket, bind, listen, and accept). It
is at 'listen' level that a server can specify for how many
On Wed, 2009-06-10 at 09:10 -0700, Vinay Nagrik wrote:
Dear Group,
How do web servers achieve scalability is bothering me for a long
time. My understanding is that an application can open one and only
one socket connection through four system calls (socket, bind, listen,
and accept). It
Complementary to what you will find in the on-line Apache documentation
at http://httpd.apache.org, and painted with a very wide brush :
When you start Apache, a single main Apache process is started.
It reads and checks the configuration, and loads a series of core and
add-on modules, as per
