On Saturday December 13, 2003 14:44, Stas Bekman wrote: > David Robins wrote: > > There are a couple of HTTP parsers in modules (e.g. > > POE::Component::Server::HTTP, HTTP::Daemon, probably in SOAP::Lite too) > > but not a standalone HTTP parser module. > > I think it's the best for the perl community if you make it part of > libwww-perl, which already has HTTP request constructor class > (HTTP::Request) and HTTP response parser (HTTP::Response). You really only > need to subclass HTTP::Message to provide the accessors for the parsed > request envelope, and the rest of the code can also re-use chunks from
I'd rather not subclass, I think it should be a separate class that _returns_ the HTTP::Request (which I am already using). Subclassing implies that the object has at all times a valid message, which it doesn't. Also returning the request doesn't give the request the baggage of an HTTP parser hanging around where it isn't necessarily wanted. > other LWP classes. See: > http://search.cpan.org/~gaas/libwww-perl-5.76/ Thanks for the suggestion, I'd be happy with making it part of libwww-perl if it would be accepted; how do I submit it for consideration as part of LWP instead of as a separate CPAN module? -- Dave Isa. 40:31
