[logback-user] Serialization improvement

[Alf Kristian Støyle]

Thanks Ceki, good to know.

Cheers,
Alf


On 24 April 2013 11:51, Ceki Gülcü <ceki at qos.ch> wrote:

> Hi Alf,
>
> Aiming for end of the month, but it might slip.
>
>
> On 4/24/2013 11:02 AM, Alf Kristian Støyle wrote:
>
>> Hi all!
>>
>> Does anyone have a guesstimate for when version 1.0.12 will be released?
>>
>> Cheers,
>> Alf
>>
>>
>> On 5 April 2013 16:43, Alf Kristian Støyle <alf.kristian at gmail.com
>> <mailto:alf.kristian at gmail.com**>> wrote:
>>
>>     Done:
>>
>>     http://jira.qos.ch/browse/**LOGBACK-829<http://jira.qos.ch/browse/LOGBACK-829>
>>
>>     Cheers,
>>     Alf
>>
>>
>>     On 5 April 2013 14:28, ceki <ceki at qos.ch <mailto:ceki at qos.ch>> wrote:
>>
>>
>>         Hi Alf,
>>
>>         The parent and childrenList fields in Logger should not be
>>         serialized. Could you please create a jira issue regarding this
>> bug?
>>
>>         --
>>         Ceki
>>         65% of statistics are made up on the spot
>>
>>
>>         On 04.04.2013 12:55, Alf Kristian Støyle wrote:
>>
>>             Hi everyone.
>>
>>             First off, my first mail on the mailinglist, thanks for
>>             logback, it is
>>             awesome :)
>>
>>             We had a problem in our project that our serialized object
>>             graph was way
>>             too large.
>>
>>             After digging, we found that a referenced
>>             ch.qos.logback.classic.Logger
>>             was the cause. A serialized object was about 27 kB, after
>>             making the
>>             referenced logger static, the serialized size was about 4,7kB
>>
>>             ch.qos.logback.classic.Logger has several transient fields,
>>             but parent
>>             and childrenList are not. My guess is that when serializing
>>             a logger,
>>             you then implicitly serialize every referenced logger inn
>>             the logger
>>             tree. Am I correct?
>>
>>             Since the readResolve method is only dependent on name,
>>             every field
>>             could be made transient, problem solved?
>>
>>             Cheers,
>>             Alf
>>
>>
>>         ______________________________**___________________
>>         Logback-user mailing list
>>         Logback-user at qos.ch <mailto:Logback-user at qos.ch>
>>         http://mailman.qos.ch/mailman/**__listinfo/logback-user<http://mailman.qos.ch/mailman/__listinfo/logback-user>
>>         <http://mailman.qos.ch/**mailman/listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user>
>> >
>>
>>
>>
>>
>>
>>
>> ______________________________**_________________
>> Logback-user mailing list
>> Logback-user at qos.ch
>> http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user>
>>
>>  ______________________________**_________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20130424/129a961e/attachment.html>