Difference between revisions of "NetMsgTypes"
From BRL-CAD
(Drop INFO from name.) |
|||
Line 66: | Line 66: | ||
|- | |- | ||
|align="center"|250 | |align="center"|250 | ||
− | |[[FullHostListREQ]] | + | |[[FullHostListREQ]]* |
|- | |- | ||
|align="center"|255 | |align="center"|255 | ||
− | |[[FullHostList]] | + | |[[FullHostList]]* |
|- | |- | ||
|align="center"|300 | |align="center"|300 | ||
− | |[[NewSessionREQ]] | + | |[[NewSessionREQ]]* |
|- | |- | ||
|align="center"|305 | |align="center"|305 | ||
− | |[[NewSession]] | + | |[[NewSession]]* |
|- | |- | ||
|align="center"|400 | |align="center"|400 |
Revision as of 14:15, 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 Generic Templates
GenericOneByteMsg | GenericTwoBytesMsg | GenericFourBytesMsg |
GenericMultiByteMsg | GenericOneStringMsg |
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:
MsgTypeID | Description |
---|---|
0 | Failure |
5 | Success |
100 | RemHostNameSET |
150 | DisconnectREQ |
200 | NewHostOnNet |
250 | FullHostListREQ* |
255 | FullHostList* |
300 | NewSessionREQ* |
305 | NewSession* |
400 | GeometryREQ |
405 | GeometryMANIFEST |
410 | GeometryCHUNK |