[ezmlm-www] scaling ezmlm-www 1.4x

[Glen S. <ro...@as...>]

The new mod_perl support in 1.4 seemed very interesting...but the script 
design doesn't seem to scale.  

Since I have 300 groups here, I had (several versions ago) decided to keep 
each config.pm file separate, so the system doesn't concurrently clobber the 
config.pm file when it (potentially) simultaneously updates or 
creates/deletes groups.

The problem with separate config.pm's, is that perperl (like mod_perl) gets 
confused about cached session variables, even when they come from the same 
script at different URLs.  So the messages listings for one group will appear 
when another is requested.

The only way I see to fix this is to load the list of groups into an array 
that specifies what the archive path is, driven by the index counter which is 
embedded in the URL.  This function is what a list of groups provides in the 
config.pm today.

Since the flat file is unsafe, it seems that a database is the faster and more 
scalable way to go.  I don't think performance from building the list 
dynamically from the filesystem would be adequate, unless all the values were 
static, except the group name/path.

Thoughts?


-- 
Associate.com - THE Place to Associate!                   http://associate.com
Is Your E-mail Group Here?   See http://associate.com/faq/your-group-here.html