Dear Log,
Dang. My module XML::RSS::Timing is great, and XML::RSS::TimingBot (an LWP::UserAgent subclass) is great, but when I implemented Etag/If-Modified-Since logic, I forgot the need to recompute the "when can I check next" time if I get a 304 -- which, since 304s are contentless, means I need to have the timing data cached from last time -- and that means that I need to add methods to marshall it and store it in the database. Hooboy. XML::RSS::TimingBotDBI users, look for a new not-backwards-compatible version coming soon.
