> Does anyone out there rely on live class > (template, message catalog, whatever) reloading in their live, > production application? > > .... and what critical benefit does this offer?
I've used live class reloading on a production system a few times, but it always felt "wrong" to me. :) However, keep in mind that the ease of development means some people are going to use Tapestry for things that normally would be handled by a scripting language. In some of those situations live class reloading in production may make sense. I understand the problems with giving people too many options. However it can be really tricky to decide what should be configurable and what need to be fixed. I wouldn't want to use a word processor that only allowed me to type in Times Roman because that was the only font the developers used and they didn't see any reason others would need to use anything different. It seems that the real advantage of having fewer options would be when it lets you keep the code base simpler, but in this case it isn't like you plan to remove the live class reloading capability. It will still be needed for development. But personally it wouldn't hamper any of my current projects if it were turned off in production. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
