Difference between revisions of "NetMsgTypes"

(Common Header Byte Format)
Line 42: Line 42:
 
|-
 
|-
 
|align="center"|15
 
|align="center"|15
|[[NewHostOnNetINFO]]
+
|[[DisconnectREQ]]
 
|-
 
|-
 
|align="center"|20
 
|align="center"|20
|[[FullHostListREQ]]
+
|[[NewHostOnNetINFO]]
 
|-
 
|-
 
|align="center"|25
 
|align="center"|25
|[[FullHostListREQFAIL]]
+
|[[FullHostListREQ]]
 
|-
 
|-
 
|align="center"|30
 
|align="center"|30
 +
|[[FullHostListREQFAIL]]
 +
|-
 +
|align="center"|35
 
|[[FullHostListREQOK]]
 
|[[FullHostListREQOK]]
 
|-
 
|-

Revision as of 08:54, 4 December 2008

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)
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