variable names

In another thread I wrote:

My own interest lies more in the area of improving the naming of some of 
the config file directives to make them more intuitive, and seeing the 
documentation move into a wiki, so it can be collectively improved upon 
(easily). As a new user to the project, I have a window of opportunity 
to address some of these things while I still see the project as an 
outsider.

One variable name change I proposed is (see earlier posting for more 
details):

The LogFile variable name is used in both logfile group config
files and service filter config files, and means different things in
each.

I'm sure this came about for historical reasons, but wouldn't it make
sense to add a more accurately named alias for the latter case, such as
LogFileGroup?


Another:

One thing I've found a bit puzzling is that both logfile
group config files and service filter config files can
reference filters, though it isn't clear what order the
filters are ran in. I would have expected to see something more like:

Filter = ApplyStdDate | OnlyService foo | RemoveHeaders


Any thoughts on whether these changes make sense and whether they could 
be implemented in a way that maintains backwards compatibility?

The last item might make overrides harder. I don't know if adding or 
subtracting (can you do that?) a filter has a practical use, but if it 
does, you'd have to override the whole "Filter" line with a new one.

  -Tom

-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/