It's all fun until someone loses an eye. What if i look at your API output and assume it's json (only got unique items) but it's rjson? Or whatever? The most important thing when adding another layer to a protocol is identification. So, please, put the whole altered object into a rjson root node so it's clear what we're dealing with.
Correct me if I'm wrong, but isn't this what Content-type is for?
RJSON: compress JSON to JSON
41–45 of 45 posts
Re: RJSON: compress JSON to JSON
#42dogada, do you have any results showing both size reduction, and speed of compression/decompression vs. other methods?
Re: RJSON: compress JSON to JSON
#43It's all fun until someone loses an eye. What if i look at your API output and assume it's json (only got unique items) but it's rjson? Or whatever? The most important thing when adding another layer to a protocol is identification. So, please, put the whole altered object into a rjson root node so it's clear what we're dealing with.
I agree that identification is important issue, but IMO it's protocol level issue. RJSON is not protocol, it's algorithm. Someone will prefer to wrap all in {"rjson": ...}, someone like {"format": "rjson", "data": ...} and so on. I belive, algorithm itself should create as less limitations as possible.
The ideal place to handle this is (as pointed out above) content negociation - specifically as 'application/rjson+json'
Re: RJSON: compress JSON to JSON
#44Earlier quoted context omitted.
hey look, I found this http://research.microsoft.com/en-us/projects/jszap/
They are using gzip compression level 1. Bogus.
Re: RJSON: compress JSON to JSON
#45It's all fun until someone loses an eye. What if i look at your API output and assume it's json (only got unique items) but it's rjson? Or whatever? The most important thing when adding another layer to a protocol is identification. So, please, put the whole altered object into a rjson root node so it's clear what we're dealing with.
I agree that identification is important issue, but IMO it's protocol level issue. RJSON is not protocol, it's algorithm. Someone will prefer to wrap all in {"rjson": ...}, someone like {"format": "rjson", "data": ...} and so on. I belive, algorithm itself should create as less limitations as possible.