Difference between revisions of "NetMsgTypes"
From BRL-CAD
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==NetMsg Generic Templates== | ==NetMsg Generic Templates== | ||
The GSNet Protocol provides several Template classes to be used or extended from. | The GSNet Protocol provides several Template classes to be used or extended from. | ||
Revision as of 16:31, 25 January 2011
NetMsg Generic Templates
The GSNet Protocol provides several Template classes to be used or extended from.
- Generic One Byte Msg
- Generic Two Byte Msg
- Generic Four Byte Msg
- Generic Multi Byte Msg
- Generic One String Msg
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 | Name | Description |
|---|---|---|
| 0x0050 | Failure | Uses Generic One Byte Msg. |
| 0x0051 | Success | Uses Generic One Byte Msg. |
| 0x0100 | RemHostNameSET | Uses Generic One String Msg. |
| 0x0150 | DisconnectREQ | "MsgType Only" NetMsg and has no body. |
| 0x0200 | NewHostOnNet | Uses Generic One String Msg. |
| 0x0250 | FullHostListREQ* | Not Implemented Yet |
| 0x0255 | FullHostList* | Not Implemented Yet |
| 0x0300 | NewSessionREQ* | |
| 0x0305 | NewSession* | |
| 0x0310 | LogoutSession | |
| 0x0400 | GeometryREQ | Uses Generic One String Msg in addition to custom fields. |
| 0x0405 | GeometryMANIFEST | |
| 0x0410 | GeometryCHUNK | Uses Generic Multi Byte Msg. |
