Hi Oleg, > Execution of HTTP requests still requires a worker thread per > connection. This limitation I intend to tackle next. The plan is to > provide an HTTP protocol layer based on the existing HttpCore API that > can handle an arbitrary number of connections with just a handful of > threads. There are several possible implementation strategies to choose > from. If anyone is interested in discussing the options before I get > down to hacking please let me know.
I have taken a look at asyncweb earlier this week. They use a different style of parser for the message headers, so they can feed in data as it arrives. The parser elements then fire soem kind of event whenever a token as been parsed. I'm not sure whether that's what you have in mind. http://docs.safehaus.org/display/ASYNCWEB/Home If you throw some ideas into the ring, I'll give you my 0.02€ :-) cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
