Commit e6fe7ff8 authored by Anders Blomdell's avatar Anders Blomdell
Browse files

Merge branch 'master' of

parents cda634f8 f6f91400
......@@ -666,6 +666,63 @@ LabComm assumes that, while the transport may drop packets, there will
be no bit errors in a received packet. If data integrity is required,
that is delegated to the reader and writer for the particular transport.
\subsubsection{Representation of hierarchical data types}
For a type that contains fields of other user types, like
typedef struct {
int x;
int y;
} Point;
sample struct {
Point start;
Point end;
} line;
LabComm encodes both the flattened signature and the
typedef which allows the hierarchical type structure to be
The avro encoding is quite similar.
The \verb+Line+ example, corresponds to the two schemas
{"namespace": "example.avro",
"type": "record",
"name": "Point",
"fields": [
{"name": "x", "type": "int"},
{"name": "y", "type": "int"}
{"namespace": "example.avro",
"type": "record",
"name": "Line",
"fields": [
{"name": "start", "type": "Point"},
{"name": "end", "type": "Point"}
which is encoded in an Object Container File as
\subsubsection{Fetures not in LabComm}
Avro has a set of features with no counterpart in LabComm. They include
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment