>>>>> "BR" == Brock Rozen <brozen@webdreams.com> writes:
BR> Agreed, it is a tough problem. Could you think of a way to do it if we
BR> had a daemon?
Oh, sure. In-core access is generally quick if the data structure is small
enough. (This wouldn't be huge, just a single hash.) The problem is that
under the current run-once-for-each-message setup, you have to read in the
state and write it back out for each invocation, which implies another
painful layer of locking and a slew of other time consuming things.
BR> If a daemon is in store for 2.0,
2.0? Try x.y, where if x==2, y!=0. Most likely, x==3 or so.
BR> Majordomo has definetly come to the point where it is being heavily
BR> used and is facing problems and situations it never had to contend
BR> with. The big leagues are here...
I think the big leagues have been here for over a year, when the major
services started offering Majordomo lists to their customers.
I really wish that some enterprising person who's not me would go through
the feature lists of other MLMs and figure out what we could be doing
better. Don't read the code, just the feature lists, and talk to people
who use those MLMs to see how well things work. I really want a handle on
Smartlist's automatic bounce handling, which I think is Big Feature Numero
Uno (TM), but that's my opinion. Smartlist does it all with something like
thirty lines of code, too, but most of it is a really ugly big regexp.
- J<
Follow-Ups:
References:
|
|
