At 12:05 AM -0500 2005-03-15, Forrest Aldrich wrote:
I gather this, from all the searching I've done. I've not really found any useful information about scaling and high-availabilty/redundancy in the FAQ or anywhere else.
There is some scalability information in the FAQ. Go to the FAQ Wizard and search for "performance". If you want more details, you'll need to go to the archives of the mailing list where people talked about things that have been summarized in the FAQ.
There's also been some information that's been shared privately -- if you find the people that have talked publicly about how they have gone about handling scalability or HA issues, they may be willing/able to share additional details with you that they have not made public.
The HA solution will very likely be solved with a stable database/backend hook where we can store/retrieve Mailman's information -- standard scalablity on that side will be relatively straightforward.
There is a MySQL MemberAdapter.
I've not looked into the MyslqMembership hack yet. Has anyone used this?
I know they have, because it wouldn't exist otherwise. However, I'll let the appropriate speak up for themselves.
-- 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, 1755SAGE member since 1995. See <http://www.sage.org/> for more info. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users 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-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
