Hi Sai,

This is admittedly not my area of expertise, but I personally don’t see any 
issue with adding an additional MIME type for GraphSON 1.0. If you can get a PR 
submitted sometime in the next 2 weeks or so I don’t see any reason why this 
couldn’t be included in 3.7.0.

Regards,

Cole Greer

From: Sai Phanindhra <phani8...@gmail.com>
Date: Tuesday, June 27, 2023 at 9:39 AM
To: dev@tinkerpop.apache.org <dev@tinkerpop.apache.org>
Subject: [Discuss] Proposal to introduce new mime type to support non-typed 
Graphson-1.0
Hi all,
   In the graph implementation i'm working on, we return text json format
of GraphSON for the http apis. Existing implementation of Tinkerpop
uses GraphSONMessageSerializerGremlinV1d0
as the serializer for GraphSon-1.0(application/vnd.gremlin-v1.0+json). This
serializer does not implement the interface MessageTextSerializer which is
needed to serialize/deserialize graph query response as string and vice
versa. Customers who intend to use GraphSon-1.0(
application/vnd.gremlin-v1.0+json) are blocked due to this behavior.

I have the following proposal to mitigate this issue.

1. Use Serializer GraphSONMessageSerializerV1d0 as the serializer for
GraphSon-1.0(application/vnd.gremlin-v1.0+json) for Http APIs
2. Or Introduce a new mime type (say application/vnd.gremlin-v1.0+json-text)
or something similar and use GraphSONMessageSerializerV1d0 serializer to
unblock customers who intend to use Graphson-1.0

   If there are no objections, I'll proceed with these changes and offer a
pull request for review. If time permits, I would like to include this
change in the upcoming Tinkerpop release(3.7.0?)

--
Thanks and Regards,
Sai Phanindhra
Warning: The sender of this message could not be validated and may not be the 
actual sender.

Reply via email to