I chose do use an EvaluatorCollection because order does not matter. With a
Filter the order is obviously important and a linked list is the ideal
solution. When an evaluator causes a flush the buffer is sent and the
remaining evaluators do not get a chance to process the LoggingEvent.
The AppenderSkeleton.FilterEvent method is pretty much self-contained and does
the filtering in about 20 lines of code. Just the EvaluatorCollection class
itself is many times that size plus is introduces related classes. Have you
ever had a need to attach more than 4 or 5 evaluators to an
