Dan Gottlieb wrote:

> Hi,
> I'm new to Python and I'm considering using Quixote for my next
> project.  I currently develop in C#/asp.net, but it feels like the
> framework adds a lot of overhead to what are fairly simple web apps.
> I've read through the Quixote docs, but I have one questions.
> Currently, I use output caching of complete pages (varying on a
> querystring param)


On a side note: there's nothing wrong with query strings, but it's worth
playing with a noun-then-the-verb approach in your URLs (e.g.
'/clients/bgates/orders/115/display'). Quixote was designed with this
kind of structure in mind, and it can lead to a much
easier-to-understand application, both internally and externally. (The
REST (REpresentational State Transfer) community has taken this idea to
great lengths, and some light reading of their literature might prove
illuminating to you (as it was to me).)


> to take most of the load off my server and database.
> Is there an equivalent caching module for Quixote?


I'd never try to convince someone /not/ to write their own
implementation of anything, but it's worth keeping in mind that you
could put a proxy caching server /in front/ of Quixote, instead of
trying to build one inside it.

Squid is probably the best-known free proxy caching server. I understand
that there are a number of Win32 ports of Squid, in various states of
repair.

I'm not sure whether rolling your own caching strategy or trying to
configure Squid will turn out to be more work. But if your target is
production-quality-code rather than the value of the learning experience
of writing your own, you should give it some thought.

Best,

-- Graham