Maarten Bosteels wrote:
I guess you forgot to rename the interface itself ;-)
Yes, I did. :-)
From http://en.wikipedia.org/wiki/Encoder "An encoder is a device, circuit, transducer, software program, algorithm or person that converts information from one format, or code to another..." So I think calling it Encoder is appropriate, but I have no string feeling about the name of the interface. The terminology also used in MINA: http://mina.apache.org/report/trunk/apidocs/org/apache/mina/filter/codec/ProtocolEncoder.html
If there is an established terminology for instance in Mina, than that should be taken into consideration. However, being unfamiliar with Mina, I was a little surprised by the use of the term Encoder.
I have no idea how much work it is to support encoders in the logback.xml file. I mean, we should be able to tell logback to use a XXXAppender with a ZZZEncoder ?
If you can somehow reasonably express it in XML format, Joran can parse it, at least that's my experience so far. So, I would not worry about the parsing part and would concentrate on the "programmatic" API.
Regards Maarten
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ logback-dev mailing list [email protected] http://qos.ch/mailman/listinfo/logback-dev
