Difference between revisions of "NetMsgTypes"

Line 3: Line 3:
 
    
 
    
 
==Common Header Byte Format==
 
==Common Header Byte Format==
+
All [[IBME_GeometryService#NetMsg_Class|NetMsgs]] will contain a uniform header:
 
   
 
   
 
{|border="1"
 
{|border="1"
Line 21: Line 21:
 
|UUID (16 bytes)
 
|UUID (16 bytes)
 
|}
 
|}
 +
 +
 +
 
   
 
   
 
==NetMsg Opcodes==
 
==NetMsg Opcodes==
 +
Some [[IBME_GeometryService#NetMsg_Class|NetMsgs]] will need to have custom bodies.  Here is a list of [[IBME_GeometryService#NetMsg_Class|NetMsgs]], their related MsgTypes, and links to details on that specific [[IBME_GeometryService#NetMsg_Class|NetMsg]]:
 +
 
   
 
   
 
{|
 
{|

Revision as of 07:31, 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)
Opcode int (4 bytes)
MessageUUID UUID (16 bytes)
RegardingMessageUUID UUID (16 bytes)



NetMsg Opcodes

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:


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


OPCODE Description
100 GeometryREQ
105 GeometryREQFAIL
110 GeometryMANIFEST
115 GeometryCHUNK