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 (JIRA)" <ji...@apache.org> on 2016/09/02 14:55:20 UTC

[jira] [Closed] (TINKERPOP-740) Serializer Handshake

     [ https://issues.apache.org/jira/browse/TINKERPOP-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-740.
--------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 3.2.2)

I sense that this issue won't be possible. Serializer configuration has gotten pretty deep and in some cases dynamic. It won't be possible to send that kind of stuff back in a handshake.

> Serializer Handshake
> --------------------
>
>                 Key: TINKERPOP-740
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-740
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver, io, server
>    Affects Versions: 3.0.2-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>
> Might be nice if Gremlin Server offered some way to tell the driver what serializers it had (sorta thinking specifically of gryo) so that it could try to use the same ones on the client.  That way the user wouldn't need to hand configure them to be the same and if some class wasn't present the driver could fail early with a clear error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)