-> >>Maybe we should organise a plug in architecture for commonly used
-> >>website components like this would be helpful.  Anybody thought of this?
-> >
-> >Every web framework has dreamed of this sooner than later... I would
-> >certainly love to see a quixotic component spec, and if there'd be
-> >such a thing I'd be happy to program against (for ;) it.
->
-> I'd join in too.
->
-> I'd love to see something that was component-oriented enough so that I
-> could, for example, decide whether to use a relational database, or
-> ZODB, or just a bunch of text files to handle persistence. Something
-> that works "out of the box" with only Quixote as a requirement (or at
-> least only depended on third-party Python packages, but not on other
-> installed software) would be tremendously helpful.

Hmm.  A community-driven 'quixote-addons' project that started with
session managers for ZODB, Durus, PostgreSQL, and text files would
be useful for at least two reasons:

* provide an out-of-the-box functioning persistent session manager,
        which is one of the more frequent needs on the list;

* provide useful examples of how to use those various backends ;).

I'd be happy to donate my SQL persistence example & make any
reasonable changes to it that were suggested.

--titus