Difference between revisions of "NetMsgTypes"
From BRL-CAD
(→Common Header Byte Format) |
|||
Line 12: | Line 12: | ||
|- | |- | ||
|MessageLength | |MessageLength | ||
− | | | + | |int32 (4 bytes) |
|- | |- | ||
|MsgType | |MsgType | ||
− | | | + | |int32 (4 bytes) |
|- | |- | ||
|MessageUUID | |MessageUUID | ||
− | | | + | |String (Variable bytes) |
|- | |- | ||
|HasRegardingUUID | |HasRegardingUUID | ||
Line 24: | Line 24: | ||
|- | |- | ||
|RegardingMessageUUID | |RegardingMessageUUID | ||
− | | | + | |String (Variable bytes) |
|} | |} | ||
Line 36: | Line 36: | ||
|- | |- | ||
|align="center"|0 | |align="center"|0 | ||
− | |[[ | + | |[[Failure]] |
|- | |- | ||
|align="center"|5 | |align="center"|5 | ||
− | |[[ | + | |[[RemHostNameSET]] |
|- | |- | ||
|align="center"|10 | |align="center"|10 | ||
Line 67: | Line 67: | ||
|align="center"|50 | |align="center"|50 | ||
|[[NewSessionREQOK]] | |[[NewSessionREQOK]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|align="center"|100 | |align="center"|100 |
Revision as of 12:10, 25 November 2009
Common Header Byte Format
All NetMsgs will contain a uniform header:
Element | Length |
MessageLength | int32 (4 bytes) |
MsgType | int32 (4 bytes) |
MessageUUID | String (Variable bytes) |
HasRegardingUUID | Boolean (1 byte) |
RegardingMessageUUID | String (Variable 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 | Failure |
5 | RemHostNameSET |
10 | RemHostNameSETOK |
15 | DisconnectREQ |
20 | NewHostOnNetINFO |
25 | FullHostListREQ |
30 | FullHostListREQFAIL |
35 | FullHostListREQOK |
40 | NewSessionREQ |
45 | NewSessionREQFAIL |
50 | NewSessionREQOK |
100 | GeometryREQ |
105 | GeometryREQFAIL |
110 | GeometryMANIFEST |
115 | GeometryCHUNK |