Re: [GSTP-devel] Command opcode

[<ale...@ne...>]

>> Will stay 16 bit, an 8 bit field would would misalign the header.
>>
>
> Oki. What are the alignment issues? (4 byte align? On what platforms
> does that matter?) If there are more "non-nessecary" bits in the header=
,
> perhaps we should save them in a "padding/reserved for future expansion=
"
> field?

I had a quick look in the protocol, and we're not really well aligned
anywhere, so I think we should just forget about alignment.
Alignment is silly anyway, a protocol should not have to care about CPU
boundaries. It's easy to work around with memcpy() anyway.

I've modified the create command, changed all fd's to 16 bit, and modifie=
d
the command and reply opcode to 8 bit, and will commit this to the CVS an=
y
time now :)

//Alexander