[spambayes-dev] db_* binaries for Windows, DB_RECOVER

[Richie Hindle]

[Skip]
> Isn't SQLite supposed to be an embedded SQL engine?  If so, where's the
> database and how is it shared across (for example) two instances of
> hammiefilter?

The database is just a file.  It supports multithreaded operation, and as
far as I can tell at a quicj glance that extends to multiprocess
operation.  You just use a different connection in each thread.

Tim, or anyone who knows - is ZODB (without ZEO, which as I understand it
is essentially what Skip suggests below) shareable across
threads/processes?

> I think the cleanest way to do this would be to run a server which simply
> fronts a pickle.  All apps would talk to it for reading and updating the
> info.  You run into performance problems with network overhead and it makes
> deploying all applications that much more complex.

This is something I've talked about in the past (but talk is cheap) and
which Neale Pickett kind of implemented with hammiesrv.  hammiesrv is a
message-classifying XMLRPC server, whereas you seems to proposing more of
a database server, but the underlying idea is the same.  I'd envisaged
pop3proxy becoming a component of a generic spambayes server, which serves
or proxies POP3, SMTP, HTML/HTTP, XMLRPC and any other protocols we need.
With the exception of XMLRPC, it's all that already (and it even has a
non-human HTTP client in the shape of proxytee.py).

But as you say, it's another installation/maintenance headache.

Hmm, it seems talk is still cheap.  8-)

-- 
Richie Hindle
richie at entrian.com