On Mon, Feb 14, 2011 at 5:29 PM, Howard Lewis Ship <[email protected]> wrote: > I'm starting to wonder whether Tapestry should, in production mode, > not even check for file changes. All the related code could be > converted to no-ops and placeholders, and the portion of the code that > even has to decide when to check for file changes could be removed.
It seems like you'd want some way to be in production mode but still have the checks for file changes. Some people are using this feature. I know I have used it in some production settings. Would it make sense to have it check for file changes in non-production mode, not check in production mode, but have a configuration option that will force the checks to take place even when it is in production mode? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
