Github user okram commented on the issue:

    https://github.com/apache/tinkerpop/pull/351
  
    Adding my email on dev@ to here.
    
    I’m not following this PR too closely so what I might be saying is a 
already known/argued against/etc.
    
        1. I think we should go with @robertdale proposal of int32, int64, 
Vertex, uuid, etc. instead of Java class names.
        2. In Java we then have a `Map<String,Class>` for typecasting 
accordingly.
        3. This would make GraphSON 2.0 perfect for Bytecode serialization in 
TINKERPOP-1278.
        4. I think that if a Vertex, Edge, etc. doesn’t have properties, 
outV, etc. then don’t even have those fields in the representation.
        5. Most of the serialization back and forth will be `ReferenceXXX` 
elements and thus, don’t create more Maps/lists for no reason. — less chars.
    
    For me, my interests with this work is all about a language agnostic way of 
sending Gremlin traversal bytecode between different languages. This work is 
exactly what I am looking for.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to