[ 
https://issues.apache.org/jira/browse/TINKERPOP-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251858#comment-17251858
 ] 

ASF GitHub Bot commented on TINKERPOP-2472:
-------------------------------------------

FlorianHockmann commented on pull request #1369:
URL: https://github.com/apache/tinkerpop/pull/1369#issuecomment-748196014


   I think @jorgebay's intention with TINKERPOP-1696 was to avoid any external 
types in a publicly facing API as it would make it much harder for users to 
update to a newer version of Gremlin.Net when we switch the JSON library if 
they have used these interfaces, e.g., because they have implemented their own 
serializers.
   
   That problem is of course still there. But I also don't see a good solution 
for this. I at least couldn't get the approach to work that @jorgebay suggested 
in the ticket to use `dynamic`. I also wouldn't want to put the serialization 
logic in a separate package for this.
   
   But overall this problem doesn't have a high priority in my opinion and it's 
also completely independent of this PR basically. If we want to further discuss 
how to tackle it, then I'd suggest that we move the discussion into the comment 
section of that ticket.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> GraphBinary support in .NET
> ---------------------------
>
>                 Key: TINKERPOP-2472
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2472
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: dotnet
>    Affects Versions: 3.4.8
>            Reporter: Florian Hockmann
>            Priority: Major
>
> Support GraphBinary in Gremlin.Net.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to