Re: [Mailman-Developers] documentation for config.pck elements?
![](https://secure.gravatar.com/avatar/161c79db9d8d7992bb95608ccc94f85e.jpg?s=120&d=mm&r=g)
what I'm suggesting is that TMDF
TMDA == ``Tagged Message Delivery Agent''
sorry.
implement and supply a Mailman membership-management plugin for just this purpose.
You've lost me. What is a Mailman membership-management plugin?
The thing we've been talking about. The thing virtclassed in MemberAdaptor.py and derived/instantiated in OldStyleMemberships.py. The thing that implements the membership-management API.
Granted, it's more work than you wanted to do, but it doesn't have to be that much more, as you too can use a Python marshal for persistence; the upside is it's a promised interface.
Mmmm.. Promised interface..
![](https://secure.gravatar.com/avatar/a930430c7f9705b71a65f341c4191a2b.jpg?s=120&d=mm&r=g)
"DM" == Dan Mick <dmick@utopia.West.Sun.COM> writes:
DM> The thing we've been talking about. The thing virtclassed in
DM> MemberAdaptor.py and derived/instantiated in
DM> OldStyleMemberships.py. The thing that implements the
DM> membership-management API.
Except that I think TDMA wants to be a client of MemberAdaptor, not a backend implementation of it, unless I'm confused.
-Barry
![](https://secure.gravatar.com/avatar/cae242885071d4caa483727bc35010e3.jpg?s=120&d=mm&r=g)
Dan Mick <dmick@utopia.West.Sun.COM> writes:
The thing virtclassed in MemberAdaptor.py and derived/instantiated in OldStyleMemberships.py. The thing that implements the membership-management API.
Jargon. :-)
OK, I'll see what I can figure out.
-- (TMDA (http://tmda.sourceforge.net/)) (user-level UCE intrusion prevention)
participants (3)
-
barry@zope.com
-
Dan Mick
-
Jason R. Mastaler