Hello Ralph,
In a different context I would have completely agreed with you. In this case
however, the service is already known. It's always assumed to be a variant of
"send this logging event there," is it not?
Ralph Goers wrote:
The only response I really can have to this is that it is focusing on
the wrong thing. If the desire is to allow Logback to accept remote
LogEvents then would should be identified first is the service that
would be used. Once you have that you will determine just how you want
to implement the service. For that matter, it might be decided that
choose to accept multiple ways to connect. This is the only place
serialization should come into the picture - simply as a byproduct of
what you choose to expose. And in many cases users of the service
shouldn't or wouldn't even know what serialization technique is being
used. They just call the client API passing in their language's
equivalent of the LogEvent.
Ralph
--
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
