I also wanted to suggest that perhaps instead of an xml serialization of value composites JSON may be better suited?
Smaller and already using string serialization representation for values.
Michael
Am 08.04.2009 2:53 Uhr, schrieb Rickard Öberg:
Paul wrote:
Le lundi 06 avril 2009 09:35:22, Rickard Öberg a écrit :
One consequence of this: on the server, with a REST-backend, it would be
good to have the data handled as String I think. The EntityStore loads
it, hands it off to the REST-backend, which can then directly print it
to the HTTP response output, without having to do any conversion. If
EntityState has "Object getProperty(name)" then the EntityStore would
have to convert the internal format to a ValueState object first, then
hand it to the REST-backend, which would stringify it again. If the
input/output format is String then this double conversion would be
avoided.
/Rickard
Hey,
About conversion, XML serialization and REST-backend, do you guys have
RDF/JSON in mind ? Just curious.
The REST backend already supports Java serialization, HTML and RDF as
output. Only Java serialization and HTML as input so far. JSON is on the
list of serialization formats to support. This is one of the places
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
