When admins are editing lanes through the admin interface, it can take an unpredictably long time for changes to actually show up in the OPDS feeds seen by library patrons (and by admins checking their own work). There can be up to four levels of caching in play:

• The "cachedfeeds" table's cache time
• For grouped feeds, the 15-minute delay in running the cache_opds_blocks script
• The CDN cache time
• The client's cache time, based on the Cache-Control header sent along with the OPDS feed

When someone is editing lanes, we should aggressively invalidate these caches to reduce the wait time. This is easy to do in the "cachedfeeds" table but less easy when it comes to the CDN and the client cache.