I'm +1 on the approach, tbh I'm partial to GraphBinary :D Trying to complete GraphBinary support in the GLVs for 3.4.x line seems feasible, it shouldn't be much work to implement as most of the heavy lifting was done on the server part. It would be nice to run all GLV integration tests (gherkin features) with both GraphSON3 and GraphBinary.
On Thu, May 30, 2019 at 2:54 PM Stephen Mallette <spmalle...@gmail.com> wrote: > We did a bit of a soft release of GraphBinary in 3.4.0 calling it > "experimental" which I think was a good idea since we had changes going in > right up to 3.4.0 and only had Java support. I saw that Jorge created: > > https://issues.apache.org/jira/browse/TINKERPOP-2229 > > which calls for Javascript support of GraphBinary and that made me think > that it might be smart to try to aim to add GraphBinary support to all GLVs > along the 3.4.x line of code with the idea that GraphBinary stays > "experimental" there. Then in 3.5.0 we look to make that feature official > and remove Gryo/GraphSON default configurations in favor of GraphBinary. > That gives us our first "big" feature for 3.5.0. >
