- From: cdr <_@whats-your.name>
- Date: Wed, 20 Feb 2008 19:05:01 -0500
- To: public-rdf-ruby@w3.org
- Cc: carmen rocco <_@whats-your.name>
> any stuff like 'type' and 'value' spelled out over and over in a serialization (and this necessitating the same thing in consuming/producing code) i know something's amok and refuse to go there
so its the same as the Talis format except objects of a statement are handled differently
specifically,
{"type": "uri", "value": "http://example"} is
{uri: "http://example"}
and
{"type": "literal", "value": "3", "datatype": "integer"} is
3
the main poin is always use JSON for intrinsic values like 5, even if youre describing '5 yards',
most parsers are written in Parsec, Ragel, Yacc, theyre benefit from fast value (string, integer, float) in generated C or ASM while yours requires manual casting later on inside slowscriptspace. a typical form index could end up calling Integer() 300 times in Javascript on the client, and to_string 300 times in the server for no reason other than your format ignores this native feature of JSON..
i got about a 25x speedup by getting rid of any sort of manual casting, and using the ragel generated json parser in ruby. and im not even selling a 'platform' i just got sick of the unnecesssary latency..
Received on Thursday, 21 February 2008 04:12:22 UTC