I'm interested to know if this project would be interested in accepting the following feature enhancement:
HTTP::CookieMonster provides a great, user-friendly way to get and set cookies, which Mechanize is missing. The key method names don't have any conflicts in WWW::Mechanize or LWP::UserAgent, so I suggest the functionality is merged in. This would include adding the following methods, based on the implementations in HTTP::CookieMonster:
get_cookie()
set_cookie()
all_cookies()
Rather than depending on HTTP::CookieMonster, I recommend manually merging in the methods we want. It's a small amount of code, and would eliminate the "Moo" dependency, as well as dropping the methods and procedural interface we don't need. The documentation would be simpler as well, as the complete docs would be in WWW::Mechanize.
m...@summersault.com reported on Sep 25, 2012
Details
Imported from Google Code issue 239 via archive