Hi there,
I'm currently working on a proposal on a Data Conversion Service. This
service would primarily replace the ailing JSONFormatter, with the
ability to provide some rules around how fields are converted (String ->
Date, String -> Numeric, different Date formats). This of course could
be extended to not only JSON but any format or any type that we have
converters for.
As I'm working through this process it was brought to my attention that
Spring also had a great converter and formatter service, which has many
more miles of proven capability under the belt, than what a custom
written Data conversion service would bring.
Pros:
* Already written and proven framework
* Tapping into knowledge of Spring users to write custom data
converters if the default converters don't match their needs
* Dependent on a framework that is actively being worked on, thus less
chance of "stale" frameworks/libs
Cons:
* Write and maintain data conversion framework
* Potentially having to deal with users and their Spring version conflicts
* Core dependency on another framework outside of Geode
Thoughts?!?
--Udo
