i was thinking more in line with the Loader is asked a last modified time
and that time is up to the loader what to do with it. For example the loader
could
check every 5 minutes if the database is updated

But maybe this is all not needed and just make a manual flush somewhere

johan



On 11/5/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
>
> Johan Compagner wrote:
> > Do we only need it for development mode?
> > Because if you change the database for production it should pick them up
> > (live)
> >
> > So caching turned off for development mode is a nice option that doesn't
> > matter anyway
> > But do we need it somehow also per StringResourceLoader what to do with
> it?
>
> I think it would be quite expensive generally not to cache if the
> content is from the DB. It seems to me that if you allow content editing
> of your keys you can easily manually create a link to clear the
> localizer cache on demand on the production server. If you really want
> dynamic content I don't really know if the message mechanism is the
> right way to go?
>
> Regards,
> Sebastiaan
>
> >
> > On 11/4/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> I was wondering if I could somehow turn off caching of the localizer in
> >> development mode (from the current source it doesn't look like it).
> >>
> >> The reason I ask is because now the cache is only flushed if a resource
> >> that is being watched is changed. However:
> >>
> >> * if you add a new properties file for a page or component after you
> >> already rendered the page once the cache is not cleared and it keeps
> >> finding the key=null entry in the cache.
> >>
> >> * if you add your own database string resource loader, the cache is
> >> never flushed at all.
> >>
> >> I know I can add a link to flush the localizer cache if and only if
> >> we're in development mode, but I think a Settings options could be nice
> >> to just turn off caching (my laptop is fast enough, I really don't care
> >> if it tries to resolve all the labels all the time).
> >>
> >> Regards,
> >> Sebastiaan
> >>
> >>
> >
>
>

Reply via email to