Re: Make LogEvent implementations Externalizable

2014-07-29 Thread Matt Sicker
Ralph is an API designer genius. :) On 28 July 2014 16:22, Scott Harrington scott...@sns-usa.com wrote: Just to follow up, There was no need for an enhancement request. I was able to implement my own 'PackedLayout' and 'PackedLogEventBridge' that serialize my particular LogEvents

Re: Make LogEvent implementations Externalizable

2014-07-28 Thread Scott Harrington
Just to follow up, There was no need for an enhancement request. I was able to implement my own 'PackedLayout' and 'PackedLogEventBridge' that serialize my particular LogEvents efficiently to/from byte array in exactly the way I wanted (by making some assumptions not suitable for

RE: Make LogEvent implementations Externalizable

2014-07-11 Thread Gary Gregory
/divdivSubject: Make LogEvent implementations Externalizable /divdiv /divRalph co: I hear you're gearing up for the release. Last weekend I scratched an itch of mine relating to SocketAppender - SocketServer bandwidth, and was able to reduce a 500-character message from around 1700 bytes to 700 bytes

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Gary Gregory
message /divdivFrom: Ralph Goers ralph.go...@dslextreme.com /divdivDate:07/11/2014 01:46 (GMT-05:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Matt Sicker
...@dslextreme.com /divdivDate:07/11/2014 01:46 (GMT-05:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Remko Popma
List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use that instead of the default

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Remko Popma
:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Remko Popma
. The size improvement is not negligible, which is great! Gary div Original message /divdivFrom: Ralph Goers ralph.go...@dslextreme.com /divdivDate:07/11/2014 01:46 (GMT-05:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Scott Harrington
: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use that instead

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Remko Popma
is great! Gary div Original message /divdivFrom: Ralph Goers ralph.go...@dslextreme.com /divdivDate:07/11/2014 01:46 (GMT-05:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Scott Harrington
: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use that instead

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Gary Gregory
: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use

Re: Make LogEvent implementations Externalizable

2014-07-11 Thread Ralph Goers
! Gary div Original message /divdivFrom: Ralph Goers ralph.go...@dslextreme.com /divdivDate:07/11/2014 01:46 (GMT-05:00) /divdivTo: Log4J Users List log4j-user@logging.apache.org /divdivSubject: Re: Make LogEvent implementations Externalizable /divdiv /divI’d be afraid

Make LogEvent implementations Externalizable

2014-07-10 Thread Scott Harrington
Ralph co: I hear you're gearing up for the release. Last weekend I scratched an itch of mine relating to SocketAppender - SocketServer bandwidth, and was able to reduce a 500-character message from around 1700 bytes to 700 bytes on the wire (it's easy to improve on Java's default

Re: Make LogEvent implementations Externalizable

2014-07-10 Thread Ralph Goers
I’d be afraid of breaking compatibility even now. However, I think what you really want to do is to create an ExternalizedLayout and then just use that instead of the default SerializedLayout. If you want to supply that Layout as a patch to a Jira issue it could be added at any time. Ralph