+---NOTE--- this is old, ignore.
+
+Will be deleted once I'm sure there's no information remaining that needs to
+be copied elsewhere.
+
Segment 0, byte 0 is a request code. Currently defined codes are:
0: Invoke Method
1: Get Interface List
stored at arbitrary locations in segment 0, and are referenced as an
offset into the segment.
-Data chunks which do not contain object id or references to other
+Data chunks which do not contain object ids or references to other
data chunks (i.e. they are pure data, and do not need to be altered
for marshalling) are stored at arbitrary locations in arbitrary
segments. References to these pure data chunks are encoded as a
Virtual structs are prefaced with a header, which consists of
the following, in order:
-1. 128-bit GUID of the most derived vstruct type
-2. 160-bit SHA-1 of the vstruct type info
-3. 32-bit objlist-offset of an introspection object
-4. 32-bit length of vstruct, including header, and all referenced
+1. 32-bit length of vstruct, including header, and all referenced
data chunks, which must be contiguously appended to the vstruct body
-5. 32-bit reserved field
+2. 32-bit offset of start of actual struct
+3. 128-bit GUID of the most derived vstruct type
+5. 32-bit objlist-offset of the vstruct's object handles, the first
+of which is introspection object
+6. 32-bit length of vstruct objlist in handles
+7. 32-bit offset of an area within the vstruct where the objlist can
+be copied.
+8. 32-bit reserved field
The requirement for all referenced data chunks to be contiguous with
the vstruct means that scatter-gather and zero-copy cannot be done;
process that does know the derived type). For this reason, vstructs
should generally not be used to pass large chunks of data.
-The introspection object reference may be NULL; in this case, the
-SHA-1 field is ignored.
+Likewise, object handles must be preserved even if they are only
+referenced in an unknown-type portion of the vstruct. To facilitate
+this, all handles referenced from the vstruct must be contiguous in
+the objlist (even if this means duplications), and there must be an
+area in the vstruct blob where unmarshalling code can copy the
+translated objlist.
+
+The introspection object reference at the beginning of the vstruct
+objlist may be NULL.
Op1: Get Interface List
-----------------------