Difference between revisions of "NetMsgTypes"
From BRL-CAD
Line 12: | Line 12: | ||
|int (4 bytes) | |int (4 bytes) | ||
|- | |- | ||
− | | | + | |MsgType |
|int (4 bytes) | |int (4 bytes) | ||
|- | |- | ||
Line 25: | Line 25: | ||
− | ==NetMsg | + | ==NetMsg MsgTypes== |
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]]: | 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]]: | ||
{| | {| | ||
− | !width="55" align="center"| | + | !width="55" align="center"|MsgType |
!Description | !Description | ||
|- | |- | ||
Line 68: | Line 68: | ||
{| | {| | ||
− | !width="55" align="center"| | + | !width="55" align="center"|MsgType |
!Description | !Description | ||
|- | |- |
Revision as of 07:32, 4 December 2008
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 | NewHostOnNetINFO |
20 | FullHostListREQ |
25 | FullHostListREQFAIL |
30 | FullHostListREQOK |
40 | NewSessionREQ |
45 | NewSessionREQFAIL |
50 | NewSessionREQOK |
MsgType | Description |
---|---|
100 | GeometryREQ |
105 | GeometryREQFAIL |
110 | GeometryMANIFEST |
115 | GeometryCHUNK |