Hello,<br><br>Yesterday, I created a logging.proto file for serializing a Logback LoggingEvent.<br>Still have to do the benchmarks, but based on [1] and [2] I expect it to be faster then java serialization.<br><br>[1] <a href="http://www.eishay.com/2008/11/serialization-protobuf-vs-thrift-vs.html">http://www.eishay.com/2008/11/serialization-protobuf-vs-thrift-vs.html</a><br>
[2] <a href="http://www.eishay.com/2008/11/protobuf-with-option-optimize-for-speed.html">http://www.eishay.com/2008/11/protobuf-with-option-optimize-for-speed.html</a><br><br>WDYT ?<br><br>Maarten<br><br><br><div class="gmail_quote">
On Mon, Mar 2, 2009 at 8:58 AM, Ralph Goers <span dir="ltr"><<a href="mailto:rgoers@apache.org">rgoers@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
On Mar 1, 2009, at 11:38 PM, Thorbjoern Ravn Andersen wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ralph Goers skrev:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think I've lost the point of this discussion somewhere. The subject says something about submitting events remotely yet this discussion seems to be totally about serialization. If it is really about something like a "service" to submit events than I would suggest looking at Spring remoting and some of the protocols it supports - such as Hessian or Burlap. I would argue that a discussion about how best to serialize an object is pointless without having first decided on what the service API is. For example, are you presuming that one system will log to an Appender that will forward to a server that will turn around and log the event again? Or perhaps an Appender would just forward the event to an Appender on the remote system? Or, using Spring Remoting one could imagine that the local Appender is just a client stub generated by Spring forwarding to the "real" Appender somewhere else.<br>
</blockquote>
I think the reason was that I asked Jörn to share his experiences with the appenders in Lilith and that I could not understand his conclusion :)<br>
<br>
What I am trying to get to is a simple way to "magically" transport a logging event from one instance of logback to another, where it would be processed with filters etc as any other event originated on the instance itself. The platform agnosticity implies that Java serialization is not trivial to use, hence the discussion with Jörn...<br>
<br>
Would Spring Remoting imply that Java is required?<br>
<br>
</blockquote>
<br></div>
Not necessarily. It depends on the transport protocol you use. For example, both Hessian (<a href="http://hessian.caucho.com/" target="_blank">http://hessian.caucho.com/</a>) and Burlap <a href="http://hessian.caucho.com/doc/burlap.xtp" target="_blank">http://hessian.caucho.com/doc/burlap.xtp</a>) are protocols that could be used from any language. If you look at Hessian you will see that Caucho even provides implementations for many languages. Spring remoting leverages the Caucho Java classes under the covers. Seehttp://<a href="http://static.springframework.org/spring/docs/2.5.x/reference/remoting.html" target="_blank">static.springframework.org/spring/docs/2.5.x/reference/remoting.html</a>.<br>
<font color="#888888">
<br>
Ralph</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
logback-dev mailing list<br>
logback-dev@qos.ch<br>
<a href="http://qos.ch/mailman/listinfo/logback-dev" target="_blank">http://qos.ch/mailman/listinfo/logback-dev</a><br>
</div></div></blockquote></div><br>