On Tuesday 07 December 2004 05:23, Curt Arnold wrote:
> I'm sure that you could do better with a custom wire-format than the
> current Java default serialization, however I'm not sure that you would
> see any significant advantage over custom serialization. The benefits
> for using Java custom se
I've been hinting at this for quite some time but apparently not loud
enough.
The reason there was no serious effort to preserve bw compatibility
between 1.2 and 1.3 is performance improvements scheduled for
1.3. Given that we always transmit LoggingEvent objects on the wire, a
protocol specialized
At 09:20 AM 12/5/2004, Scott Deboy wrote:
I haven't tried sending events from log4j 1.3 to log4j 1.2.8, but I doubt
deserialization would work, without more changes to serialization logic.
In 1.3, LoggingEvent contains a new field:
long sequenceNumber
The 1.2.8 code wouldn't know what to do with
On Monday 06 December 2004 21:59, Shapira, Yoav wrote:
> Hi,
> We should balance the performance aspect versus the requirement for
> serialization compatibility. I think the latter is a nice to have, but
> by no means an essential feature. I think the former is imperative for
> log4j as it is for
gEvent serialization compatibility between 1.2 and
1.3
>
>On Sunday 05 December 2004 16:20, Scott Deboy wrote:
>> I haven't tried sending events from log4j 1.3 to log4j 1.2.8, but I
doubt
>> deserialization would work, without more changes to serialization
logic.
>>
>
On Sunday 05 December 2004 16:20, Scott Deboy wrote:
> I haven't tried sending events from log4j 1.3 to log4j 1.2.8, but I doubt
> deserialization would work, without more changes to serialization logic.
>
> In 1.3, LoggingEvent contains a new field:
> long sequenceNumber
> The 1.2.8 code wouldn't
rs List
Cc:
Subject: Re: LoggingEvent serialization compatibility between 1.2 and 1.3
On Dec 4, 2004, at 6:06 PM, Scott Deboy wrote:
> MDC and LocationInfo have changed between 1.2.9 and 1.3, so if your
> logging events don't contain either of those, the 1.2.9-generated
>
On Dec 4, 2004, at 6:06 PM, Scott Deboy wrote:
MDC and LocationInfo have changed between 1.2.9 and 1.3, so if your
logging events don't contain either of those, the 1.2.9-generated
events will be deserialized successfully in a 1.3 environment
(Chainsaw V2).
Can I assume the converse is true tha
Sent: Sat 12/4/2004 1:29 PM
To: Log4J Developers List
Cc:
Subject: LoggingEvent serialization compatibility between 1.2 and 1.3
I inferred from previous comments that there may be an incompatibility
between 1.2 and 1.3 between the serialized form of LoggingEvent used by
SocketApp
I inferred from previous comments that there may be an incompatibility
between 1.2 and 1.3 between the serialized form of LoggingEvent used by
SocketAppender. Could someone summarize the current state?
p.s.: The Javadoc comment for Logger.getLogger() mispells "returned" as
"reutrned".
---
10 matches
Mail list logo
