Maik Jablonski wrote:
Oliver Marx wrote:
Well
First of all I don't think that I would use the ZODB for a TeamWare project. TeamWare will if used generate a lot of data and this is AFAIK not what the ZODB is designed. But then again - I could be wrong.
that's right for very, very, very large & active teams... packing the ZODB once or twice a day [or every hour] should avoid the data.fs from growing too big. maybe undoable transactions are quite funny for a groupware-system... so: I'd prefer the ZODB even for Group/Teamware-systems...;-)
Ok - I'm not 100% aware of how the ZODB work.
With that said and with all the debate there has been around Intranet and Zope - maybe we should consider making a framework for that? TeamWare would just be a part of it.
maybe we should walk through the products-lists at zope.org and integrate the promising ones [for groupware-functionality of course] under a single [interfaced] framework...
cheers, maik
That would make a good starting point. \Oliver
Maik Jablonski wrote:
Oliver Marx wrote:
Dear List
I am thinking of writing a Tutos frontend for Zope.
Would that be of any interest?
\Oliver
hi oliver,
what are the benefits & the surplus from this rewrite? storing your data still in MySQL [or any other relational database] and simply replacing PHP-web-interfaces with Zope/Python-Interfaces is a lot of work & maintainance for a long time [to be in sync with the Tutos-guys] without any significant advantages, isn't it?
switching the database-backend to ZODB would be interesting [maybe a 'proof on concept' for the power of ZOPE], but is even more work for one person. maybe we should think about starting a TeamWare-Project for ZOPE from the scratch...;-)
cheers, maik