Re: LockingStringBuilderEncoder ByteBuffer

2020-03-15 Thread Ralph Goers
> On Mar 15, 2020, at 2:10 PM, Volkan Yazıcı wrote: > > On Sun, Mar 15, 2020 at 6:03 PM Ralph Goers > wrote: >> After looking at the code I am sure there is something >> wrong with the logic. While you can set property >> log4j2.enable.direct.encoders to true or false it >> uses the same Enco

Re: LockingStringBuilderEncoder ByteBuffer

2020-03-15 Thread Volkan Yazıcı
On Sun, Mar 15, 2020 at 6:03 PM Ralph Goers wrote: > After looking at the code I am sure there is something > wrong with the logic. While you can set property > log4j2.enable.direct.encoders to true or false it > uses the same Encoder in either case. I am a little bit puzzled here. Which particul

Re: LockingStringBuilderEncoder ByteBuffer

2020-03-15 Thread Ralph Goers
After looking at the code I am sure there is something wrong with the logic. While you can set property log4j2.enable.direct.encoders to true or false it uses the same Encoder in either case. As for why it is not a class member variable, that would be because it wouldn’t be thread-safe if it wa

LockingStringBuilderEncoder ByteBuffer

2020-03-15 Thread Volkan Yazıcı
Hello, I want to take advantage of StringBuilder plumbing in the core module. There are two Encoder implementations: StringBuilderEncoder and LockingStringBuilderEncoder. Given JsonTemplateLayout has its own customizable recycling strategy, I can't use StringBuilderEncoder due to its TLAs. Locking