On 5/8/05, Phillip Susi <[EMAIL PROTECTED]> wrote: > I like this idea. I think one of the best and most important things > that apache is doing these days is trying to migrate away from being a > web server and towards a generic server platform. Eventually I would > like to be able to run apache to serve web content, email ( smtp as well > as pop3 ), and subversion repositories and other file shares ( possible
pop3? What happened to imap? > I'm not quite sure what you mean here, but that is probably because I'm > new to hacking on apache, so forgive me if this is a stupid question. > As I understand it now, the MPM receives data from the socket and places > it into a bucket, attaches the bucket to the brigade, and calls the > lowest level filter, passing it the bucket. Each filter in the chain > then can modify the brigade, and can pass the bucket to the next filter, > or possibly call back down the chain to the mpm to get more data. > Eventually the brigade makes it to the handler which forms a reply and > passes it back down the chain to the mpm to send out on the socket. Is > this about correct? Where do workers fit in? I'd guess the socket handling code would be single-threaded. But you can't block the entire server to handle a single request, so the request would be handled in a thread of even another process.
