1. Messages
  2. Best practice setup for Go driver development & identifying the websocket serialization format

Re: Best practice setup for Go driver development & identifying the websocket serialization format

Ray Scott <raya...@...>
 

That makes sense to me. Is there a suggested way to format data in the `data` section. I realise you can write a script to output anything you wish, but if I'm, say, wanting to do CRUD style work on a vertex, is there an efficient and non-error prone way to represent that data if I perform a read on that vertex? I'm fetching it from Go code. 



On Monday, 7 August 2017 15:06:29 UTC+1, Keith Lohnes wrote:
What you're receiving looks a lot like the `data` section of the response JSON. Not knowing what client you're using, I can't say that's normal behaviour, but I've seen http clients behave similarly. As for "setting" the response format, I believe it's however the request is serialized e.g. json is serialized back as json, kryo is serialized back as kryo.

On Friday, August 4, 2017 at 5:14:23 PM UTC-4, Ray Scott wrote:
Do you have a reference for that setting the response format? The driver documentation doesn't mention it, only that you can specify the format of the request. There is an example response in JSON, but it's nothing like what I receive as a response. This is in the Tinkerpop docs. Janus seem to have removed driver development documentation from their release.

http://tinkerpop.apache.org/docs/3.2.5/dev/provider/#_graph_driver_provider_requirements
Join {janusgraph-users@lists.lfaidata.foundation to automatically receive all group messages.