[DISCUSS] Handling of problematic GraphSON types

As part of the discussion for the pull request by Daniel C. Weber that adds support for more extended GraphSON types to Gremlin.Net [1] we identified several of those types to be problematic for non-Java languages (or at least for .NET in this case) as they don't really have counterparts in other

[GitHub] tinkerpop issue #842: TINKERPOP-1945

Github user FlorianHockmann commented on the issue: https://github.com/apache/tinkerpop/pull/842 In case someone is following here but is not on the dev mailing list:

[jira] [Commented] (TINKERPOP-1945) Add support for extended GraphSon types to Gremlin.net

[ https://issues.apache.org/jira/browse/TINKERPOP-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488898#comment-16488898 ] ASF GitHub Bot commented on TINKERPOP-1945: --- Github user FlorianHockmann commented on the

[GitHub] tinkerpop issue #842: TINKERPOP-1945

Github user FlorianHockmann commented on the issue: https://github.com/apache/tinkerpop/pull/842 > @FlorianHockmann Why would we do that? If we can construct (i.e. deserialize) e.g. a DateTime of whatever a server gives us, fine. Doesn't mean we have to send (i.e. serialize) obscure

[jira] [Commented] (TINKERPOP-1945) Add support for extended GraphSon types to Gremlin.net

[ https://issues.apache.org/jira/browse/TINKERPOP-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488868#comment-16488868 ] ASF GitHub Bot commented on TINKERPOP-1945: --- Github user FlorianHockmann commented on the