[
https://issues.apache.org/jira/browse/TINKERPOP-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043632#comment-18043632
]
ASF GitHub Bot commented on TINKERPOP-3219:
-------------------------------------------
andreachild commented on PR #3285:
URL: https://github.com/apache/tinkerpop/pull/3285#issuecomment-3628418702
It seems that the other driver GLVs already expose the serialization layer
so go is an outlier. Perhaps instead of using an exposed wrapper we can just
make the serializer public for consistency with the other GLVs.
> Add public serialization API in gremlin-go for alternative transport protocols
> ------------------------------------------------------------------------------
>
> Key: TINKERPOP-3219
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3219
> Project: TinkerPop
> Issue Type: Improvement
> Components: go
> Affects Versions: 4.0.0, 3.8.1
> Reporter: Haiyu Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0, 3.8.1
>
>
> Currently, gremlin-go only supports WebSocket transport. The serialization
> logic (GraphBinary) is internal/private, preventing developers from building
> custom transport implementations (gRPC, HTTP/2, etc.) while maintaining
> Gremlin API compatibility.
> This improvement adds a new file gremlin-go/driver/serializer_export.go with
> 5 exported wrapper functions around existing internal serialization logic:
> - SerializeRequest() - Serialize bytecode with traversal source
> - SerializeBytecode() - Convenience wrapper using default source
> - SerializeStringQuery() - Serialize string queries
> - DeserializeResult() - Deserialize response bytes
> - NewResultSet() - Create ResultSet from collected results
> These are thin wrappers with zero modifications to existing code, fully
> backward compatible, and enable the ecosystem to build alternative transports.
> Use case: Building gRPC-based Gremlin clients for production deployments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
