[Mailman-Developers] Login / User Identification Issues in MM3

[Richard Wackerbarth]

Stephen,

I'm not advocating that Postorious be THE keeper of the user information. But it would be a good candidate for the job.

What I am advocating is that the "core" message handler NOT be the keeper of ONLY PART of it.

I am perfectly happy to have the user info handled by an independent stand-alone module which is willing to take responsibility for ALL of the user profile info. It should provide a REST interface that allows other modules the ability perform authentications, manipulate the profile, etc.

Another acceptable methodology would be to store all of the data in a real relational database and allow each of the modules direct access to the database engine.

Richard

On Jul 11, 2012, at 12:12 AM, Stephen J. Turnbull wrote:

> Richard Wackerbarth writes:
> 
>> Since by far the most complicated, and most used, logins will be
>> made from the web interface, it is much more logical to allow
>> Postorius to be responsible for all of the user profile information
>> and have the core, on those rare occasions where it requires it,
>> obtain password confirmation from that source.
> 
> From the point of view of Postorius implementers, no question about
> it.<wink/>
> 
> But isn't that going to take us a long way down the road where we
> anoint Postorius the one-and-only admin interface?  If that really
> needs to be, OK, but I don't much like it.  Among other things, it
> will make the design and detailed UI of Postorius a focus of
> discussion for everybody concerned with Mailman 3.  And it makes the
> option to "build one to throw away" much more difficult -- the design
> decisions already made, and will be made in the near future, will
> probably live as long as Pipermail has (and Pipermail will continue
> for several more years, at least!)
> 
> If that doesn't scare you....<wink/>
>