On Fri, 2007-07-27 at 16:40 +0200, Roland Weber wrote: > Hi all, > > a recent communication on the user list made me aware > that we have classes Http*Parser in HttpNIO, but not in > HttpCore for the traditional IO. There, the logic is > implemented directly in the connections. I like the > structure of NIO better. > We get inquiries about tolerating bad HTTP messages on a > regular basis. Having a parser interface with a default > implementation that can be substituted would make things > easier for those users. > > What do you think? >
Roland, Please note the job parsing HTTP lines is taken care of by SessionInputBuffer / SessionOutputBuffer classes Core NIO, not by the HttpMessageParser. SessionInputBuffer and SessionOutputBuffer classes are direct equivalents of AbstractHttpDataReceiver and AbstractHttpDataTransmitter in Core Base. So, it all boils down to inconsistent class names in HttpCore Base and HttpCore NIO. In both cases one still needs to subclass abstract connection classes in order to customize the way HTTP messages are constructed. I can take care of ensuring class name consistency across modules this weekend. Oleg > cheers, > Roland > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
