Kevin Dangoor wrote:
Particularly with positional parameters, CherryPy makes it easy to construct useful, descriptive URLs. You just instantiate the object that's going to respond to some URLs and drop it in the part of the hierarchy you want. Just like that, It starts answer requests. No separate configuration needed... everything is just assembled as a Python program.
On the other hand this needlessly complicates the hierarchy. What makes perfect sense for an URL may not lend itself to a pythonic program. When pushing for ultimate accessability and usability URLs should of course be considered but that is just icing on top. Why make such a trinket a (program) design consideration?
Simon
