Changes for version 1.28 - 2004-03-13
- THINGS THAT WILL BREAK YOUR CODE
- The C<cache> parm to the constructor is no longer a set of parms to specify how the cache will be initialized. It must now be a fully-initialized cache object, probably in the Cache::Cache hierarchy.
- Existing caches will not work, because I changed the directory that they get written to. It used to go into /tmp/FileCache/WWW::Mechanize::Cached, but now will go into /tmp/FileCache/www-mechanize-cached. This is so the Windows folks can use the module, too.
- However, if you want to create your own cache object that writes to /tmp/FileCache/WWW::Mechanize::Cached, for compatibility, you can create it and pass it in.
- ENHANCEMENTS
- You can now specify your own Cache::Cache object to pass into the constructor.
Modules
Cache response to be polite