On Tue, Apr 29, 2008 at 11:35 AM, White, Tim <[EMAIL PROTECTED]> wrote: > > Would it not work for you to turn caching on and set the > modificationCheckInterval to 0? Of course this would mean no > > changes to template would be recognized (fault or otherwise). > > Unfortunately, we need them to be able to be changed after the server > has been started. > > > > Even if we created such a setting, you would presumably have to make > your cache large enough to fit all > > your templates so none of them were ever cleared from memory. > > Yes. > > > > You could probably implement this by creating a custom > ResourceManager. > > Right, that was what I was thinking...just a balance of risk between > hedging against our NFS failures, and future-proofing such code > extensions...
ResourceManager has not changed much over the years, if it helps to know that. > Thanks for the thoughts, > > > Tim > > > This communication is the property of Qwest and may contain confidential or > privileged information. Unauthorized use of this communication is strictly > prohibited and may be unlawful. If you have received this communication > in error, please immediately notify the sender by reply e-mail and destroy > all copies of the communication and any attachments. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
