On 12 November 2003, A.M. Kuchling said:
> Interesting; see http://www.masonhq.com/docs/manual/Devel.html#data_caching .
>
> For Quixote the problem reduces to "how do you cache the output of Python
> callables?" I don't know of a solution as fancy as Mason's, though you could
> easily do a little memoization wrapper around a function.

IMHO we should leave this up to whoever needs it.  If a general solution
appears, add it to Quixote.  I've mused in the past about response
caching, but never seen a real-world need for it.  Skip's the first to
bring it up publicly (AFAIK).  Smells like YAGNI to me.

> See http://www.mems-exchange.org/software/quixote/doc/session-mgmt.html for
> an explanation of session management.  I haven't seen any code specifically
> for a MySQL database.  (Probably wouldn't be a bad idea to add it, since
> MySQL is quite widely used.)

-0.9.  Quixote is database-agnostic (except for that nasty little bit
of code in SelectWidget that looks for a ZODB OID), and IMHO should
remain that way -- even to the extent of excluding all persistence code
from the core.

Of course, if it turns out that the existing scheme for session
persistence makes working with stupidbases (err, sorry, RDBMSs) really
really hard, we should fix the design.

        Greg
--
Greg Ward                          http://www.gerg.ca/
If you and a friend are being chased by a lion, it is not necessary to
outrun the lion.  It is only necessary to outrun your friend.