Add a mechanism for invalidating the front-end cache, if any. Currently it spits...