Gunnar R|nning wrote:
>
> "Daniel L. Rall" <[EMAIL PROTECTED]> writes:
>
> > > stuff that is #included() are not templates, so the handling will be
> > > different. The stuff will be cached in that it won't be read off the
> > > disk every time, but it will check file modification times or
> > > something to ensure that any changes to the included material are
> > > always immediately #included().
> >
> > That's perfect!!
>
> Nothing is perfect. What about making checking of modfication time
> configurable, because this may be unecessary overhead in some production
> systems or you may only want to check for changes every 5 minutes or so and
> not on every single request...
Yep. That was along the lines of what I had in mind, making it as
configurable as possible to give us as many choices as possible...
I figured the options would include :
1) timed expiry
2) check for reload at expiry
3) force reload at expriry
so 0 + check = Daniel / Jon, 5min + check = Gunnar, 0 + force = anyone
with suspicious modification times, etc
Of course it would be a reactive rather than proactive check/force, only
taking action at the time of the next #include() call after expiry, not
at the actual moment of expiry (but that, I hope, should be obvious...
:)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
