+1 I think that's a good idea! A client of mine recently had issues due to those checks (root-problem was a bug in the jvm implementation).
Am 15.02.2011 um 00:29 schrieb Howard Lewis Ship: > 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. > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > 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]
