>>>>> "Ian" == Ian Eiloart <[EMAIL PROTECTED]> writes:
Ian> No, you've evidently completely misunderstood me. All I do
Ian> want is for Mailman to use *exactly* the same mechanisms for
Ian> sender ACLs that it does for rosters. If that's LDAP, that's
Ian> fine. If it's SQL, that's fine. If it's flat files, that's
Ian> fine.
As Brad says, that's easier said than done. As it happens, Mailman
does (by default) use exactly the same method---it's called a "Python
pickle".
But a Python pickle is an _object_ database. LDAP is about
tree-structured databases, SQL about relational databases. It's
non-trivial to put most of the stuff in Mailman into those formats.
The problem isn't really that pickles are Python-specific, that's what
Fred Brooks would call an "accidental" obstacle. You're right, we
could, at a fairly predictable amount of effort, convert from a
Python-specific data store to a standard one accessible by a
well-defined protocol such as LDAP or SQL. The problem is that the
data used by Mailman doesn't necessarily fit those models, and we
won't know how hard the conversion is (ie, what effects there will be
on various parts of Mailman) until we do it. It's a good bet that it
will be harder than it looks.
Regards,
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
