> I'm a great believer that avoiding query strings in URL's is good > practise ( http://www.holloway.co.nz/book/9 for good arguments why).
CherryPy also supports that out of the box: class Book: def default(self, categoryName, bookId): ... cpg.root.book = Book() If you go to "http://domain/book/science/9";, CherryPy will call book.default('science', '9') > Also how > much does it complicate matters to run cherryPy under an existing > webserver? Is any functionality lost? Well, you can easily run CherryPy behind Apache (see http://trac.cherrypy.org/cgi-bin/trac.cgi/wiki/BehindApache). Since CherryPy provides a WSGI interface (although it's still experimental), you can also run your CherryPy app with any WSGI-compatible HTTP server (although I don't really see any advantage to doing this). Remi -- http://mail.python.org/mailman/listinfo/python-list
