Other ways of using tapestry (e.g. disable service reloading)

Perhaps to save many people's time on the mailing list and dev - something like an "alternatives" section in the docs for some of tapestry's features.

Personally, I'm looking at tapestry for a 3rd time in the last few years for a project and finally getting into the guts of it.

e.g.

Service Implementation Reloading

There was this thread - http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Switching-off-Reloading-of-Service-Implemenation-td5724115.html which a simple "Alternative" section in the docs could have saved a few man-hours.