Apache配置中的不同术语意味着什么？

Question

I keep coming across certain terms used in the Apache settings. While trying to understand the various discussions and Apache's docs , I need some help figuring out what some of these terms mean:

1. What is a Client?
2. What is the difference between a client and a child process? Are they the same?
3. If MaxClient = 255 , does it mean that Apache will process up to 255 page loads in parallel and the rest are queued?
4. When is a KeepAlive request used?
5. What is the relationship between a child process and the request of this child process?

Answer 1

First, I hope you understand that apache 1.3 is very very old, and therefore the documentation will generally be somewhat harder to understand than the newer documentation (ie maybe you should upgrade if you have the choice).

1. I'm not sure where "Client" is referred to by itself in the apache docs by I would assume it refers to anything connecting to an open port and communicating.

2. Again, not sure where "child" is referred to by itself, so I can't help you there.

3. MaxClient is the number of processes apache will start to handle requests. It sounds like for Apache 1.3 that what you said is accurate, apache will only handle MaxClient requests in parallel (queuing the rest up to some other maximum for the queue).

4. KeepAlive is not really a request. It is sent in the request header to tell the server that the browser supports KeepAlive. It has to do with a feature of HTTP that allow one connection to be used for more than one access. If you allow KeepAlive your server will probably get less TCP connections.

5. I'm not even sure what you're asking here so you'll need to be more specific.

Answer 2

First, note that these answers apply either to Apache 1.x, or Apache 2.x only when using the prefork mode.

1. The machine that opens an HTTP connection and sends a request.

2. No, they are not the same. An Apache child can handle one request/client at a time, but when that one is finished, the same child can handle a new one.

3. Yes.

4. It is used to keep the HTTP connection open in case the client wants to issue another request. A client can remain connected, for example, to download images and such that are associated with a web page. Having KeepAlive On improves performance for the client (user), but having it off reduces memory usage by the server. It is a trade-off.

5. The Apache process launches a bunch of children. When a request comes in, the parent (root) process picks an idle child to handle that request. When that request is finished, the child is now idle and can handle a new request.