[DIST] - Implement JSON message format

GoogleCodeExporter commented 9 years ago

The Message class is currently being serialized and deserialized together 
with everything else. We need to implement messages as JSON formatted, 
human readable, programming language and platform/JVM agnostic text.

JSON is powerful enough to represent queries etc.

While the wire representatio is JSON, we need to have a general data 
structure for representing messages that is independent of JSON while 
still following the same formal model of nested structures with named 
slots, primitive values and lists. The same data structure could be used 
for s-expressions if we decide to switch the format for whatever reason 
(e.g. interact with other "agent-oriented" frameworks).

Initially, the top-level structure need to be specified. What are the 
available attributes, what is their precise meaning. Which ones are 
required and which ones are optional.

Original issue reported on code.google.com by borislav...@gmail.com on 22 Jun 2008 at 5:23

GoogleCodeExporter commented 9 years ago

I started a description of the message structure on
http://code.google.com/p/hypergraphdb/wiki/MessageStructure

Original comment by ciprian....@gmail.com on 23 Jun 2008 at 3:23

GoogleCodeExporter commented 9 years ago

Original comment by borislav...@gmail.com on 10 Feb 2009 at 6:49

Changed state: Fixed

dopicar / hypergraphdb

[DIST] - Implement JSON message format #15