🚀 go-pugleaf

While learning assembler, I wondered about how iserver is supposed to be
used.  If two processes communicate with each other, the length of 
corresponding 'in's and 'out's has to be same, right?  For the root 
transputer exchanging data with the host, that doesn't matter, but what 
for a router process which transports iserver packets between processes,
e.g. to simulate a virtual transputer network?

Do all commercial iserver libraries use the same in/out protocol, which 
is given by the OCCAM data structures?

> Every communication, both to and from the server, is a counted array of
> bytes.  The first two bytes are a (little endian) count of the following
> message length.
>
> In OCCAM these messages can be routed as INT16::[]BYTE protocol.

An example for a data packet is the PutBlock Function:

> To server:    BYTE           Tag = 24
>               INT32          StreamId
>               INT16::[]BYTE  Data

Somehow I don't understand it.  How will the packet be sent?

-   INT16, rest as single BYTEs
-   INT16, rest as one block of BYTEs (I have no knowledge of OCCAM, sorry)
-   INT16, BYTE, INT32, INT16, rest as single BYTEs
-   INT16, BYTE, INT32, INT16, rest as one block of BYTEs

I hope there is a convention.  Or am I totally wrong?

Michael