-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Dec 12, 2008, at 1:01 AM, Jesus Cea wrote:
Studying the code, it seems easy to migrate membership to a separate
persistence system (let say, ZODB, Durus) or use a backend like
sqlite.
Any plan for that?. Any interest in patches?.
Yes, but not in Mailman 2. It's in Mailman 3 by default and any code
that helps that branch get further along will be greatly appreciated.
FWIW, I am planning on another alpha release before the end of the
year. My intent is to have the system working and usable without a
web ui, but possibly with the administrative REST interface we'd been
talking about.
You're analysis is essentially correct. For Mailman 2.2, I think
adding the weakref would be fine in principle, but the more invasive
data store changes would not be. Much better to get Mailman 3 out the
door with its real database backend.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAklCjAMACgkQ2YZpQepbvXGELgCeLRYuuovefsgt5WgAVpRZh3R7
sRQAniPRBQ9vvQ/Wgng6lbHMVYZW04NY
=Y2bn
-----END PGP SIGNATURE-----
_______________________________________________
Mailman-Developers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
