[A second note to follow up on the description of my questions around a new
JSON wire protocol.]
The most "intractable" problem with a nicer wire protocol seems to be
in dealing with iterated containers, and specifically with their types.
Consider a message like:
struct Foo {
1: required l
Folks,
[at the suggestion of a couple of committers, I'm sending this to the dev@
mailing-list. It's a little involved, and I'll write a second note, with
even more detail. Please skip if this is too much in the weeds, and with
my apologies for the details. Really am looking for advice here ...
le, which is the basis of the cross-platform test suite:
https://github.com/apache/thrift/blob/master/test/ThriftTest.thrift
Have fun,
JensG
From: Chet Murthy
Sent: Monday, October 16, 2017 9:45 PM
To: jensge...@hotmail.com ; r...@apache.org
Subject: "iterated container types" ?
Randy
