[
https://issues.apache.org/jira/browse/TINKERPOP-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362585#comment-15362585
]
ASF GitHub Bot commented on TINKERPOP-1274:
-------------------------------------------
Github user PommeVerte commented on the issue:
https://github.com/apache/tinkerpop/pull/351
Ok I thought The main point here was robustness in typing for non-java
languages. Hence why I suggested even typing things like Int and using java
classes. Honestly depending on how you compiled your PHP your basic JSON int
will be converted to `Long`. And that's the case I was highlighting.
It makes sense to ignore this if you're trying to reduce de payload but
we'll still be lacking on the non-lossiness end.
>As I see it for how I implemented the TypeDeserializer, it acts as a meta
deserializer that will read the raw text JSON sequentially, so there's no
chance there can be a mixup in the order
You can't guaranty that the order would be maintained in some languages
hence my previous comment. These languages will parse the JSON into `List<Map,
?>` then check the list and Map along the lines of what I said in my previous
post. It would be much more efficient to simply have JSON cast to `Map` and run
a simple check on keys.
> GraphSON Version 2.0
> --------------------
>
> Key: TINKERPOP-1274
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1274
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Affects Versions: 3.1.2-incubating
> Reporter: stephen mallette
> Priority: Minor
> Fix For: 3.2.1
>
>
> Develop a revised version of GraphSON that provides better support for
> non-JVM languages that consume it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
