[EMAIL PROTECTED] wrote:
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'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/
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).
How tricky is it to remap URL's to query strings in cherryPy? Also how
much does it complicate matters to run cherryPy under an existing
webserver? Is any function
Hello everyone,
I am happy to announce the release of CherryPy-2.0-beta.
CherryPy-2 is a pythonic, object-oriented web development framework.
CherryPy-2 is a redesign of CherryPy-1 (the unpythonic features have
been removed): no more compilation step, pure python source code (no
more "CherryClas
