Yeah, the JSON protocol is not really good for human editing. You *could* hack the protocol to make it do what you want, or you could just generate ruby stubs and use irb as a console to edit the configs.
On Fri, Feb 25, 2011 at 10:49 AM, Nevo Hed <[email protected]>wrote: > Hi All > > New user to thrift, planning to use thrift to communicate between multiple > components in my system > but I also was thinking of using a thrift structure to represent my app > configuration (without a service) > > I was hoping to eventually use thrifts binary encoding, by just writing the > serialized object to my file > > But till I have an console/screen for managing these configs in my app I > was > hoping to just write-out the config as JSON > using ThriftJSONString... I was hoping to see text tags in JSON, but I > see > quoted strings instead > > Wanted to see: > * > > {"cookie":{"i32":1111638355},"cfgVersion":{"i16":1},"addrBase":{"i32":-1442971648}} > *But instead I see > * {"1":{"i32":1111638355},"2":{"i16":1},"3":{"i32":-1442971648}} > *Which is far less human friendly > > Any suggestions? (os thrift just the wrong thing here?) > > Thanks! > -Nevo >
