[Skip] > Yes, I believe it still is. Most SpamBayes usage scenarios > involve just one of the applications, so there's been no > crying need to add locking so they can operate concurrently.
CVS Head (or 1.1a1 when it's out) supports using ZEO as a database backend. (It hasn't been tested much, but I have been using the ZODB (FileStorage) backend for months without any problems). I think with ZEO any potential problems would raise ConflictErrors, which you could catch (in the ZEOStorage class in storage.py, presumably) and deal with appropriately. Just a suggestion about one way to go... =Tony.Meyer -- Please always include the list ([email protected]) in your replies (reply-all), and please don't send me personal mail about SpamBayes. http://www.massey.ac.nz/~tameyer/writing/reply_all.html explains this. _______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
