You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While VALUE_EMBEDDED_OBJECT is mostly used internally for piping through things like native binary content (byte[]), it is also necessary in some cases to support native datatypes of non-JSON formats, and especially when buffering is required. Although not all backends will support such writes (in fact, most standard ones would throw an exception), there are cases where calling code knows that this is safe usage; and there is the specific case of buffering (TokenBuffer) where we can support opaque passing of such objects.
So, it may make sense to add such an optional method to make it easier to support data formats with richer set of primitives.
The text was updated successfully, but these errors were encountered:
gcxRun
added a commit
to gcxRun/jackson-core
that referenced
this issue
Feb 21, 2016
(note: follow-up from FasterXML/jackson-databind#1068)
While
VALUE_EMBEDDED_OBJECT
is mostly used internally for piping through things like native binary content (byte[]
), it is also necessary in some cases to support native datatypes of non-JSON formats, and especially when buffering is required. Although not all backends will support such writes (in fact, most standard ones would throw an exception), there are cases where calling code knows that this is safe usage; and there is the specific case of buffering (TokenBuffer
) where we can support opaque passing of such objects.So, it may make sense to add such an optional method to make it easier to support data formats with richer set of primitives.
The text was updated successfully, but these errors were encountered: