On Mon, 9 Aug 2004, Andy Lester wrote: [...] > LWP is RFC-compliant. Gisle has done a marvelous job of making sure it > does just what the RFC says. > > WWW::Mechanize is a subclass and superset of LWP that does more > "browser-like" stuff. Mechanize is meant as a browser in an object, > whereas LWP does the strictly correct thing. > > That division of labor has served us well for a few years now. [...]
I guess that makes a fair amount of sense. RFC 2965 really is dodo-like in its dead-ness, though. I think it's unusual in that respect: Most RFCs are much healthier, even if they're frequently ignored. The only practical uses of 2965 code I can think of are on intranets (*maybe*), and 2109 cookies (viz, those that have a Version attribute of 1 and arrive in a Set-Cookie: header). AFAICT, it makes sense to treat 2109 cookies as if they were 2965 cookies. Not sure if LWP does so, though, and I don't imagine it's a burning issue in many users' minds <wink> John
