On Fri, Jan 28, 2011 at 9:04 PM, Stephan Beal <[email protected]> wrote:
> a) in large JSON outputs the extra copies of the keys add significant > amounts to the data size. JSON is often the format of choice because it's so > compact. > b) In most JSON-reading languages (primarily JS), it is trivial to > normalize the data to the format you demonstrate. > i forgot (c): JSON objects do not have a specified ordering of keys, which means that in the "fat" format it is impossible to know whether the order of the keys is the same as the query (and it is likely not, since most JSON impls use associative arrays/maps, sorted on key string). This particular impl uses insert-order ordering, but when it goes to JS/PHP/C++/Ruby/whatever space the code my rearrange it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
