[Mailman-Developers] Users, persistent storage, caches, etc.
jdennis at redhat.com
Thu Jul 6 20:33:55 CEST 2006
> On Thu, 6 Jul 2006, emf wrote:
> > Barry, I've read about your SQLAlchemy work and look forward to seeing
> > that checkin ;)
> > 1.) I have to have a concept of user to really improve the user
> > interface. ...
My apologies, I have yet to read Barry's SQL work so perhaps the issue
of how a user is defined has been greatly enhanced over the current 2.1
model. But from earlier work I did on "adapters" I can say Ethan is
right on with respect to needing per-list information on a user, rather
than just a global user. Perhaps the right model is a hierarchical
resolution of attributes, e.g.
Does this list force an override of this attribute?, else
Does the site force an override of this attribute?, else
Is the attribute defined for this user for this list?, else
Is the attribute defined in the user's global properties?, else
Is the attribute defined for the list?, else
Is the attribute defined in the site's global properties?, else
attribute is undefined
John Dennis <jdennis at redhat.com>
Red Hat Inc.
More information about the Mailman-Developers