>>>>> "DW" == Dave Wolfe <dwolfe@risc.sps.mot.com> writes:
DW> Bug #1 is a bit of a sticky wicket. I chose to adopt the policy that if
DW> the -l option is specified (a default list) then a list name must *not*
DW> be specified in the request, reasoning that requests sent to a specific
DW> list-request alias shouldn't be specifying other lists anyway, [...]
DW> Does anyone object vehemently to that dichotomy?
The way the Majordomo 2 parser works is that giving the -l option only sets
the default list. That is, it pretends that there's a "default list blah"
at the beginning of the message. Fortunately the code that adds the
default list to the command line is in one place instead of spread all over
the place, so things like this are easy to change. It could be made to
always insert the list if a default is set, and never insert one otherwise.
This _would_ clear one of those parser ambiguities that some may remember
my veins popping over.
The problem is that we would then have two separate command structures,
depending on where the command is sent. While making the list name
optional at the -request address makes sense, mandating that it not be
there is something altogether different. And to head off the obvious
request to make it configurable, I would say that for something like this,
all servers need to behave the same.
Personally I don't like -request addresses anyway, so I'm biased for
eliminating the parser ambiguity.
- J<
Follow-Ups:
References:
|
|
