Difference between revisions of "NetMsgTypes"

(Common Header Byte Format)
Line 19: Line 19:
 
|MessageUUID
 
|MessageUUID
 
|UUID (16 bytes)
 
|UUID (16 bytes)
 +
|-
 +
|HasRegardingUUID
 +
|Boolean (1 byte)
 
|-
 
|-
 
|RegardingMessageUUID
 
|RegardingMessageUUID

Revision as of 08:27, 25 November 2009

Design icon.png This page contains the design document for an enhancement or feature. The design should be considered a work in progress and may not represent the final design. As this is a collaborative design, contributions and participation from other developers and users is encouraged. Use the discussion page for providing comments and suggestions.


Common Header Byte Format

All NetMsgs will contain a uniform header:


Element Length
MessageLength int (4 bytes)
MsgType int (4 bytes)
MessageUUID UUID (16 bytes)
HasRegardingUUID Boolean (1 byte)
RegardingMessageUUID UUID (16 bytes)

NetMsg MsgTypes

Some NetMsgs will need to have custom bodies. Here is a list of NetMsgs, their related MsgTypes, and links to details on that specific NetMsg:


MsgType Description
0 RemHostNameSET
5 RemHostNameSETFAIL
10 RemHostNameSETOK
15 DisconnectREQ
20 NewHostOnNetINFO
25 FullHostListREQ
30 FullHostListREQFAIL
35 FullHostListREQOK
40 NewSessionREQ
45 NewSessionREQFAIL
50 NewSessionREQOK


MsgType Description
100 GeometryREQ
105 GeometryREQFAIL
110 GeometryMANIFEST
115 GeometryCHUNK