```
0 1 2 3 4 5 6 7 octet
+-------+-------+-------+-------+-------+-------+-------+-------+
-| conn-id | conn-type | |
+| conn-id | conn-type | fields |
+-------------------------------+---------------+---------------+
| conn-spec
...
+---------------+---------------+-------------------------------+
| data
...
++---------------------------------------------------------------+
+| unique-id |
++---------------------------------------------------------------+
```
| | 0x0001: socket |
| | 0x0002 - 0xFFFF: reserved for future use |
| | |
+| `fields` | A collection of flags indicating presence |
+| | of additional fields after the variable |
+| | length `data` part. The additional fields |
+| | will start after a possible padding for |
+| | aligning to a 8 octet boundary. |
+| | Defined flag values (to be or-ed): |
+| | 0x0001: `unique_id` present (only needed for |
+| | `shared ring` connection in live |
+| | update streams). |
+| | |
| `conn-spec` | See below |
| | |
| `in-data-len` | The length (in octets) of any data read |
| `data` | Pending data: first in-data-len octets of |
| | read data, then out-data-len octets of |
| | written data (any of both may be empty) |
+| | |
+| `unique-id` | Unique identifier of a domain |
+| | |
In case of live update the connection record for the connection via which
the live update command was issued will contain the response for the live