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 2018/10/30 12:52:00 UTC
[jira] [Assigned] (TINKERPOP-1942) Binary serialization format
[ https://issues.apache.org/jira/browse/TINKERPOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette reassigned TINKERPOP-1942:
-------------------------------------------
Assignee: Jorge Bay
Affects Version/s: 3.3.4
[~jorgebg] just looking at your branch a bit. i see you have the serializer stuff all in gremlin-driver module. is that just out of convenience? or do you envision that this sort of serialization is only relevant to network communications?
will it ultimately live in gremlin-core with the other IO formats?
> Binary serialization format
> ---------------------------
>
> Key: TINKERPOP-1942
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1942
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Affects Versions: 3.3.4
> Reporter: Jorge Bay
> Assignee: Jorge Bay
> Priority: Major
>
> We should provide a binary serialization format designed to reduce serialization overhead and minimizing the size of the payload that is transmitted over the wire.
> It could be implemented in a very similar way as Kryo support but with interoperability in mind and ultimately we could fade Gryo out, as now with the GLVs it doesn't have a role to play.
> The main benefit would be the performance improvement, making serialization and deserialization processing time negligible on both the server and the client.
> Background: https://lists.apache.org/thread.html/13e70235591853801bab16ed457ee4f56f3dfe2d1c5817c34a036408@%3Cdev.tinkerpop.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)