Dmitry Olshansky wrote: > No. Conceptually replace does replaceInto but creates a new appender > each time. This is the overhead replaceInto means to avoid. That's much clear now, thanks! -- Shriramana Sharma, Penguin #395953