At 9:04 PM -0500 2006-03-09, Bob Puff wrote:
> I think we're drifting here from a logical format. If there is to be shared
> ownership, I think that needs to be done with a different database. It could
> be a nightmare from the admin side if you group things by who wants to own
> what lists, rather than by domain.
Actually, his proposed scheme does make sense for a larger-scale
environment. Indeed, that's the second-most scalable way I know of
to do it. The most scalable would have some sort of side index
system and use good hashing algorithms to avoid having a billion
subdirectories under /usr/local/mailman/lists/com/ and maybe just a
few hundred under /usr/local/mailman/lists/info/.
For smaller environments, you might want a different option.
I think what we really need is some way to guarantee that any of
several different suitable formats could be used, some of which might
be more easily understood at a glance, others which might be more
complex but also more scalable.
--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
LOPSA member since December 2005. See <http://www.lopsa.org/>.
_______________________________________________
Mailman-Developers mailing list
[email protected]
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
