On Fri, Apr 6, 2018 at 2:59 PM, Xiao Ma <xma...@gmail.com> wrote:
> The NonBlockingJsonParser introduced in 2.9 is very useful. However, it
> doesn't provide the optimization for UTF-8 encoding as in
> UTF8StreamJsonParser. Is there a plan to provide a non-blocking JsonParser
> with UTF-8 encoding optimization?
Implementation is actually UTF-8 optimized, and only works on UTF-8
(or compatible, that is, 7-bit US-ASCII) content.
There is no character-based alternative at this point so for other
encodings only blocking parser exists.
-+ Tatu +-
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.