On Thu, 2009-07-23 at 05:59 -0700, ricardo13 wrote: > Hi, > > > ricardo13 wrote: > > > > > > > > Eric Covener wrote: > >> > >> On Sun, Jul 19, 2009 at 11:50 PM, ricardo13<ricardoogra...@gmail.com> > >> wrote: > >> > >>>> One question for I undestand the sequence of hooks. > >>>> Do It means that firstly worker.c processes sockets (accept > >>>> connections), > >>>> after other modules processes the hooks (post_read_request, > >>>> translate_name, map_to_storage, etc..)?? > >> > >> Yes, although there are connection-related hooks that run in-between > >> the two things you mentioned. > >> Is pre-connection a hook ? > >> > >> What's the best hook for manipulate a pool of requests ?? > >> > >> I've understood that hooks like as (post_read_request, create_request, > >> ...) manipulates ONLY ONE request. > >> Now, I would like to manipulate sockets as worker.c, but manipulate > >> requests object before the content generator. > >> > >> Thank You > >> Ricardo > >> Ricardo > >> > >> -- > >> Eric Covener > >> cove...@gmail.com > >> > >> > > > > >
Can you do something about your mail client? As you can see here, you seem to be putting your message inside of the mail you quoted. It is extremely difficult to read what you are asking. worker.c is a MPM, which the docs say: The server ships with a selection of Multi-Processing Modules (MPMs) which are responsible for binding to network ports on the machine, accepting requests, and dispatching children to handle the requests. The request_rec is not setup until the socket is handled by a child thread/process, and so outside of the scope of worker.c Can you re-explain, clearly, exactly what it is you are trying to achieve? I understand it is some sort of QoS load balancing. Tom