json-lib-user

[Matt S. <ms...@ac...>]

I'm taking a look at the new json-lib 2.0, it looks great!

It seems as though a lot of the general configuration about 
serialization has been taken out in the JsonConfig object.  This doesn't 
appear to be Thread-safe; if you have two threads serializing different 
objects (presumably with different configurations), one will clobber the 
other's JsonConfig.

Is this correct?  Any workarounds, or is there a different/better way to 
do the serialization configuration (particularly excludes for me, right 
now) in a Thread-safe manner?

Thanks,
Matt