On Fri, Nov 21, 2008 at 12:47 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > There are two caches actually: > > One cache manages the values of sling:vanityPath properties, which may > be used as the domain root or root path. This cache is of course not > flushed on each modification in the repository. Rather this cache is > managed by listening to sling:vanityPath modifications and updating to > the point information. > > The other cache will cache actual resolutions of request URLs to > resources. Since this may also be a time-consuming job optionally > involving reading multiple sling:vanityPath properties. This second > cache is -- probably -- very hard to maintain just by listening to > sling:vanityPath changes. For this reason, I think it is ok to start > with a "clear on modification" approach. > > We may still implement a more intelligent cache later, should we find > out, that the cache hit-ration is to low.
These caches sound very good for now. > Of course, over time, it may get confusing if many sling:vanityPath > properties are set. I think to cope with that, we can provide a > "management" interface (thinking of Felix Web Console integration right > now), which may show domain and path roots. That woulde be nice, but already a simple query reveals all configs: //element(*, sling:VanityPath)[EMAIL PROTECTED]:vanityPath] I think doing everything with sling:vanityPath is fairly easy to understand, better than different mechanisms at different places. Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
