Michael Carter wrote: > Correct me if I'm wrong, but wouldn't that result in a single thread > being responsible for reading and parsing all HTTP traffic for your > application?
I believe so, yes. > I can see how this would be OK in cases where the app-level processing > is signifigantly more intensive than the HTTP parsing. But there are a > number of use-cases where this isn't the case. Take a comet server for > example: There's very little work for the other threads to do besides > idle for a while, then send back a small body. For these cases we need > *each* thread parsing HTTP requests. I'm a bit skeptical, to be honest. Although libevent and lighttpd are two completely different codebases, both take the same general approach to HTTP as a single-threaded, single-process server that eschews (where possible) select() or poll(). I think the results are pretty clear: parsing HTTP is not the bottleneck. :-) -- Matthew Weigel hacker unique & idempot.ent _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
