> You've probably considered this but is there a reason you can't just
> have the thrift IDL specify a string, and put JSON text into that
> string before it goes through thrift, and parse the JSON string in
> your app on the other end when it comes out? Then you don't have to
> worry about modifying thrift at all.
Well, it's not really JSON, but something with similar characteristics --
Brian picked up the key one.
I might need to support folks using "vanilla" thrift which limits my
options. Your suggestion is less invasive then my ideas, requiring a
helper library to unpack the strings into the nested/recursive types. And
vice-versa.
/r$
--
STSM, WebSphere Appliance Architect
https://www.ibm.com/developerworks/mydeveloperworks/blogs/soma/
