You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Stephen Mallette <sp...@gmail.com> on 2016/06/29 11:44:28 UTC
[DISCUSS] GraphSON 2.0
Note that a PR for GraphSON 2.0 has been submitted:
https://github.com/apache/tinkerpop/pull/351
While I haven't reviewed in full myself yet, I think that this is a very
nice set of changes. Given past discussions on this list in relation to
this issue, I think we should all be happy with what was produced.
GraphSON 2.0 should be interesting to driver devs (who i hope can review
this PR a bit) because it will allow them to build their own type
interpretation systems more easily. For example, the python driver could
choose to convert a GraphSON Vertex into a Python Vertex object so that the
users is working with actual Graph objects and not Map/List.
Anyway, please have a look - hopefully we can get this merged in this week
in time for 3.2.1.
Re: [DISCUSS] GraphSON 2.0
Posted by Dylan Millikin <dy...@gmail.com>.
I'll try and have a look sometime tonight.
Cheers.
On Wed, Jun 29, 2016 at 7:44 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> Note that a PR for GraphSON 2.0 has been submitted:
>
> https://github.com/apache/tinkerpop/pull/351
>
> While I haven't reviewed in full myself yet, I think that this is a very
> nice set of changes. Given past discussions on this list in relation to
> this issue, I think we should all be happy with what was produced.
>
> GraphSON 2.0 should be interesting to driver devs (who i hope can review
> this PR a bit) because it will allow them to build their own type
> interpretation systems more easily. For example, the python driver could
> choose to convert a GraphSON Vertex into a Python Vertex object so that the
> users is working with actual Graph objects and not Map/List.
>
> Anyway, please have a look - hopefully we can get this merged in this week
> in time for 3.2.1.
>