Kevin Dangoor wrote: >.... > > I know that you've been thinking along the lines of a "product API". > What I've been shooting for is the ability to compose applications > using standard Python mechanisms. Install an egg, import the class and > hook up an instance to your tree... that would hardly even need > documentation, because it's just the "python way". There were some > problems with configuration and such that made this not work properly > with CP2.1. I believe those problems are resolved in CP2.2. >
Agreed. The ability to compose your application tree from your RootController using classes instances is one of the best features of CherryPy/TurboGears and the one that most impressed me when I've first seen it. Hence, hardcoding the mount point inside the application class sounds like a bad thing that goes against this functionality. Maybe at some point in the future (at least once CherryPy 2.2 is stable) it would be cool to have (or use) a simple system like routes to gain total URL flexibility, better if still centered around the RootController class. Maybe at some point CherryPy itself will provide something like this. :-) Ciao Michele
