Hi all, The previously discussed removal of OpProcessor from TinkerPop 4 will mean that the RequestMessage format will need to change. This means that we will need to introduce new versions of the serializers as the RequestMessage/ResponseMessage format is tied to the version of the serializer. The old serializers were also tied to WebSockets in that there were header bytes used to identify the MIME type of the serializer. For HTTP, we will be removing this since the standard way of expressing this is to use the Content-Type and Accept headers. Also, since the response will be one large object rather than many small responses (like it was with WS), the serializers will be changed to support streaming of one large message.
In terms of serializer support for the GLVs, I think it makes sense for them to only support GraphBinaryV4 as it should be superior in terms of performance. There are some slight type support differences so those will have to be addressed. GraphSONV4 will exist in the server for tools that prefer a more JSON document like approach to handling their data. This means that the server will support only GraphSON4 (both typed and untyped) and GraphBinary4 but none of the older serializers as they are either very similar or not recommended at this point. Regards, Valentyn
