On Fri, Nov 21, 2008 at 10:03 AM, Vidar Ramdal <[EMAIL PROTECTED]> wrote: >> This _is_ expensive and therefore absolutely requires caching. >> Therefore, we will introduce a small (something like 1000 entries or >> so), which may be used to directly map incoming requests to resources. >> The cache is managed very simply: on each change in the resource tree, >> the cache is just dropped. > > I'm not thrilled about the idea of dropping the cache on every change. > In our application, there will be changes maybe every minute, > effectively leaving the cache unusable.
The cache should not be dropped on every repository change, but simply on all changes to a "sling:vanityPath" property (and all other properties involved in the vanity mechanism), which is simple to do in an observation manager. If the vanityPath requires a vanity node type, one can simply listen for that one and then look if one of the vanity path config properties has changed. Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
