In Need of Javascript/JSON expert

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.....
 
Well somebody that can we can show what the problem is and that can see it they can help us and what the work may cost?
 
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.....
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/.

As to intercepting the traffic between you and the server; this is a typical man in the middle attack scenario, however any decent online service should have taken steps to circumvent this. In short you want communication destined to/from server to be relayed via a proxy; this custom proxy app would then in turn adjust the JSON before relaying it to the server or the client.

So are you saying no this service operates e.g. on an open channel i.e. no encryption, no state maintenance on the server or client, etc...
 
Can't tell if you are sarcastic ? Elaborate a bit ?
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 :whistle:.
 
[)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 :whistle:.

Like?
 
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
 
[)roi(];17449514 said:
Yeah just look how well it worked for XML / SOAP
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(];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.

I agree, XML is heavy and clunky. If your contracts are automatically generated by the IDE for example, then SOAP is not that bad though.

Today there are arguably better alternatives to JSON, hence I said JSON is so yesterday :whistle:.
 
[)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 :whistle:.
No XML?! Web dev?
 
Hamster already mentioned one: Protocol Buffers & another alternative to that is MessagePack, or even MongoDB's BSON.

One of the biggest downfalls of XML / SOAP is the byte cost for sending data. JSON is lighter but still quite expensive, hence we needed alternatives like Protocol Buffers, MessagePack and BSON.

Aside from byte cost; XML / SOAP is also costly to process i.e. deserialise / serialize; JSON is slightly better but you need only count the number of JSON frameworks to appreciate that it's not so simple and the opinions vary greatly about the best way to deal with the many JSON stream pitfalls.

It's probably far too early to tell how successful the new alternatives will be, given it takes time for standards to be entrenched.
 
Last edited:
It's not really addressing why people shifted from XML to JSON to Protocol Buffers, ...
e.g. Numbers are still stored as characters; the number 123 still takes 3 bytes (assuming utf8 encoding), whereas with MessagePack and ProtocolBuffers it can be packed into 1 byte.
 
Last edited:
[)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.

I hear you
 
XML :sick:

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).
 
XML :sick:

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).
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.
 
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
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...

Basically what you are asking is for someone to analyse how the swf app works. This takes times and it's no guarantee of success, for example: had they simply encrypted the data, the man in the middle is all but nullified, or they opted to maintain session state on the server, etc...

First off the bat, this isn't particularly intriguing task for a developer; well I certainly don't think it is.
Secondly in your reply, you mentioned it's an swf app; which means t's most likely built with ActionScript, so you might just be better off finding someone who is familiar with decompiling swf files.

Alternatively you can always see if a beer bribe or two... couldn't be enough for your source to share more details.
 
Top
Sign up to the MyBroadband newsletter
X