Did you publish any of this? I'd like to read it.
Nope. All private conversations with Eric and Bryan. Unfortunately, I've lost all mailboxes I had while I was at AOL, so I can't pull those messages back up.
Sorry, guy. ;-(
Mailman 3 will definitely be database backed, via an interface that allows different back-ends to be pluggable. My prototypes use BerkeleyDB through Python 2.3's standard bsddb module.
Cool.
However, my experience with transactional BerkeleyDB's performance doesn't make me confident about using it for the queue runner subsystem. We'll very likely stick with the file-based qrunner architecture, although I've worked out a way to use only one file per message.
My experience with Berkeley DB has been that you store the actual content in files, and you put meta-data in the database (with a field that tells you the full path to the file). The file is touched only once in creation, read one or more times (on message delivery), and then deleted when all copies have been delivered. All other activity occurs within the database.
Used that way, it's blindingly fast, unbreakable, and amazingly efficient with memory. However, I'm not convinced that using a standard Python access module is the way to get the best out of it -- I don't know how reliable that module is, and it could be a significant drain on the capabilities of Berkeley DB itself.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
