[Pythoncard-users] ZODB as persistence mechanism

I'm diving into ZODB for a business project so I thought I'd volunteer to
take on some level of responsibility for investigating what it would take to
use ZODB as the persistence mechanism for PythonCard stacks. I think ZODB
has a lot going for it that might make it quite a good match for PythonCard.
At the same time, using ZODB will not be something that could just be tacked
on after the fact. I think the entire framework would have to be refactored
to accommodate the needs of ZODB.

In any case, I'll find out what the issues are and take the lead on the
analysis. If anyone wants to join me please feel free to do so. Here are two
good articles to get you started.

http://www.amk.ca/zodb/guide/zodb.html

http://www.zope.org/Documentation/Articles/ZODB1

---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."