I think if we move BeanJsonConverter into common and rename it (since it handles things that aren't beans), we can hide all JSON serialization and parsing logic behind this and JsonSerializer. Code will then never have to worry about how to deal with JSON, it can deal with java primitives, collections, and beans.
On Mon, Feb 9, 2009 at 5:18 PM, Louis Ryan <[email protected]> wrote: > We currently have two JSON bindings in the Java Shindig codebase. The > JSON-lib one isnt used (?) and adds a significant amount of code. I believe > that it is faster than the JSON.org implementation but I dont know if we > have a critical performance need here yet. Id be in favor of removing it, > we > can always add back later. Thoughts? >
