[Home]MessageFragments

HomePage | RecentChanges | Preferences

(incomplete, see also http://old.gale.org/gag/proto )

Messages are composed of fragments. The order of fragments in a message doesn't matter. Unknown fragments should be ignored; this will allow the format to be extended without sacrificing compatibility.

Fragment Data Types

 ID Type
 0 UCS-2 text.
 1 Arbitrary binary data.
 2 128-bit date/time stamp: 64-bit seconds since epoch, 64-bit second fraction.

 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
 | sec. high | sec. low  | frac. hi. | frac. low |
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

 3 32-bit signed integer.
 4 Nested fragment list.

Current fragments:

Fragments in key requests and responses:

Fragments in a return receipt:

deprecated/obsolete fragments:

custom fragments

experimental fragments


HomePage | RecentChanges | Preferences
This page is read-only | View other revisions
Last edited February 18, 2004 18:27 by h34-aclarke.sv.meer.net (diff)
Search: