Mark Sapiro <[EMAIL PROTECTED]> writes: > Anyway, my intent is not to critique other solutions, but to say that > I would much prefer to see a directory inserted rather than a > host_name appended. This has performance advantages and might fit > better with a scheme of "hashed" intermediate directories to help > sites with very large numbers of lists. Once you add the > infrastructure for one intermediate directory, it may become simpler > to add more intermediate directories. > > I.e, for the initial cut, split the lists/<listname> structure into > lists/<hostname>/<listname> and similarly for archives/private and > archives/public.
Actually, implementing the lists/<hostname>/<localpart> and archives/(private|public)/<hostname>/<localpart> was one of the first things I have implemented, as it is one of the easiest parts and had been mentioned at http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/VirtualHosting It's not as clean as I'd like it to be yet, though: There is the very same code to create those directories in both Mailman/Site.py and Mailman/Archives/Archives.py (two nested try: blocks with the os.umask() where the inner try finally calls os.makedirs()). OTOH, one can argue that Site.py and Archives.py handle fundamentally different things and just happen to need the same code. Still, I always become wary when I see the same code in different places :) > Anyway, it's your project, but I think we'd all welcome a complete > solution to this problem. Good. Let's see how far I can get. Gruß, Hans Ulrich Niedermann _______________________________________________ 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
