etienne_marais
Honorary Master
- Joined
- Mar 16, 2008
- Messages
- 15,093
[)roi(];17449514 said:Yeah just look how well it worked for XML / SOAP
Can't tell if you are sarcastic ? Elaborate a bit ?
[)roi(];17449514 said:Yeah just look how well it worked for XML / SOAP
If I'm understanding correctly the secrecy is to maintain your "advantage"; the one you hope to attain? JSON btw is readable by a human, so comparison of before and after should in theory be a simple matter of examine he before and after JSON/.Well as i said in my PM the game we are playing has been patched from creating a cheat which we used to speed up a few things. I was told via a person that has bypassed the Server call as it may be that if i have a really sharp JSON coder at hand i should look into the JSON side of things(thats always the story.) We wont tell you but we will give you an idea. SO as old as it may be seem thats what i am looking for.....
In a popularity contest who wins: JSON or XML?Can't tell if you are sarcastic ? Elaborate a bit ?
[)roi(];17449784 said:In a popularity contest who wins: JSON or XML?
Whilst XML has far more things (i.e. functionality, features, ...) going for it; in a popularity contest who wins; personally I haven't used much if any used XML in any apps I've built in the last 6 years; JSON has always seemed the more logical choice.
Today there are arguably better alternatives to JSON, hence I said JSON is so yesterday.
Just because the idea wasn't implemented once doesn't mean it doesn't work. Suicide not using some sort of schema on large systems or integration work.[)roi(];17449514 said:Yeah just look how well it worked for XML / SOAP
[)roi(];17449784 said:In a popularity contest who wins: JSON or XML?
Whilst XML has far more things (i.e. functionality, features, ...) going for it; in a popularity contest who wins; personally I haven't used much if any used XML in any apps I've built in the last 6 years; JSON has always seemed the more logical choice.
Today there are arguably better alternatives to JSON, hence I said JSON is so yesterday.
No XML?! Web dev?[)roi(];17449784 said:In a popularity contest who wins: JSON or XML?
Whilst XML has far more things (i.e. functionality, features, ...) going for it; in a popularity contest who wins; personally I haven't used much if any used XML in any apps I've built in the last 6 years; JSON has always seemed the more logical choice.
Today there are arguably better alternatives to JSON, hence I said JSON is so yesterday.
Like?
Hamster already mentioned one: Protocol Buffers & another alternative to that is MessagePack, or even MongoDB's BSON.Like?
It's not really addressing why people shifted from XML to JSON to Protocol Buffers, ...TOML
[)roi(];17449890 said:It's not really addressing why people shifted from XML to JSON to Protocol Buffers, ...
e.g. Numbers are still sene as characters; the number 123 still takes 3 bytes (assuming utf8 encoding), whereas with MessagePack and ProtocolBuffers it can be packed into 1 byte.
Yeah it really depends on size and the type of the data you're transmitting. i.e. number heavy volumes are crazy big in JSON, not to mention the encoding issues you can encounter when working with multi-localization, hence MessagePack, ... seem like an obvious or inevitable choice.XML
JSON is a great default because of ease of use and developing with it and it is supported everywhere. Bonus points if you marshal from a protocol buffer struct or similar.
So easy to change it later if it really causes that big a bottleneck but I'm yet to see it. Our trading system uses JSON as comms between services and it is plenty fast under load. No need to complicate the developers' lifes and early optimize to something else already (leave that option open for one day should you need it).
Unlocked "unlimited money," and "god mode" yet?Hells Teeth if nothing else i started a kewl debate. Very interesting!

Not exactly, JSON has many applications, not only for intra-client/server messaging but it can also simply be used for local configuration, state, etc...Well i am not a by any way a coder or coding expert. what happens now is when we want create our speed up as it may there is now a window saying please wait for build to complete. After hearing about the issue at hand we were inform via a reliable source that the company has now installed a Server callback which prevents instant building and checks available resources first. This reliable source then went on to say that if we need to do what they are doing they will not tell us how but will only say we must look very closely at the JSON side of the swf file we are using and that it sends a callback to the server .
I hope this makes sense to you
regards