On Tue, Oct 2, 2018 at 10:34 PM Nilson Santos Figueiredo Jr. <[email protected]> wrote: > > Hi, > > I have a particular use-case where we're trying to optimize some code which > uses Jackson to generate less garbage. > The desired outcome here is to do something similar to what > com.fasterxml.jackson.databind.ser.std.RawSerializer does, but avoiding the > toString() conversion. > Everything is working fine, except I can't avoid the duplication of byte[] > buffers due to not having access to the private _writeBytes - I either need > to convert those to char[] or to String. This is of course not ideal, as it > then becomes a source of garbage. > > Is there a particular reasoning behind not making writeBytes as part of the > public interface? > Or is there some other obvious ways of injecting byte[]s into the output > stream which I've missed?
I am not sure I follow exactly what you are attempting to do here, so could you give an example of hypothetical calls you would make? What kind of input would come in as byte[], other than binary data to be base64 encoded? -+ Tatu +- -- You received this message because you are subscribed to the Google Groups "jackson-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
