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
Similar to FasterXML/jackson-dataformats-binary#399 (and others) (based on changes for FasterXML/jackson-core#1089)
we need to allow re-configuring of recyclers used for recycling ObjectReaderModifier/ObjectWriterModifier instances: mostly for new Project Loom (where ThreadLocal based approach won't work well) but also allow users to use more optimal pooling in general.
Ideally changes would go in 2.16, leaving default impl in use but allowing re-configuration.
The text was updated successfully, but these errors were encountered:
cowtowncoder
changed the title
Convert ObjectReaderInjector/ObjectWriterInjector to use new (2.16) pluggable RecyclerPool instead of hard-code one
Convert ObjectReaderInjector/ObjectWriterInjector to use new (2.16) pluggable RecyclerPool instead of hard-coded one
Sep 30, 2023
Actually, I forgot what ThreadLocal is used for here: it is not for Object recycling but for "AOP" style injection of modifiers.
Hence cannot be simply replaced -- if changes needed, need to think through using something else.
Similar to FasterXML/jackson-dataformats-binary#399 (and others) (based on changes for FasterXML/jackson-core#1089)
we need to allow re-configuring of recyclers used for recycling
ObjectReaderModifier
/ObjectWriterModifier
instances: mostly for new Project Loom (whereThreadLocal
based approach won't work well) but also allow users to use more optimal pooling in general.Ideally changes would go in 2.16, leaving default impl in use but allowing re-configuration.
The text was updated successfully, but these errors were encountered: