I have a confession to make. I participated in something horrible recently. I hope that sometime, somewhere, I can forgive myself.
ASON /eɪ - sahn/, short for ASCII JSON is a serialization encoding for JSON invented by Del Johnson, used to tunnel large JSON requests to an application through an Oracle Web Center Interactive portal gateway without triggering errors from the gateway.
ASON is an "ASCII encoding" of JSON text which simultaneously
- is larger than the original JSON text,
- is completely unreadable, and
- adds considerable CPU processing costs to the encoding and decoding of the text.
The steps needed to serialize a message using ASON are simple:
- Build the JSON text as usual.
- Iterate over the characters in the JSON text, building a new string by:
- Converting each character to its decimal numeric representation, and
- separating the decimal numbers with commas.
Deserializing the message is the inverse of serialization.
An example ASON message is:
[Edit: Great. I can't even look up ASCII correctly anymore. "H feel..." Bah. Thanks, Del.]
I am familiar with JSON part, as such it is horrible but it's implementations can manage the secure number encodings, and some frameworks, such as PHP's execution of JSON, always do the secure number encodings of everything.
cbass, Del asserts that ASON has an advantage there because the characters are encoded unsigned.
I need a shower.
Terry, I'm not sure what you are referring to.
The problem we had was that WCI (http://www.function1.com/2007/09/know-your-traffic-flow-part-ii/) was blowing chunks on large, JSON-bodied requests going to a back-end application (http://blog.integryst.com/webcenter-interaction/2010/04/03/the-perils-and-pitfalls-of-the-wci-gateway-transformer/). Seems like it didn't like all the characters.
Now I really need a shower.