Difference between revisions of "NetMsgTypes"
From BRL-CAD
(First round of formatting/editing for NetMsg Types. Eventually, this will be a Doxy file.) |
|||
Line 9: | Line 9: | ||
==NetMsg MsgTypes== | ==NetMsg MsgTypes== | ||
− | Some | + | 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: |
+ | |||
+ | '''NOTE:''' This list is not uptodate as of 1.25.11 | ||
+ | |||
− | + | {|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #666699; padding: 0;" | |
− | {| | + | |style="border: 1px solid #666699; background-color: #666699; color: #FFFFFF; width: 90px;"|'''MsgType ID''' |
− | + | |style="border: 1px solid #666699; background-color: #666699; color: #FFFFFF; width: 90px;"|'''Name''' | |
− | + | |style="border: 1px solid #666699; background-color: #666699; color: #FFFFFF;"|'''Description''' | |
− | |||
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0050 |
− | | | + | |style="border: 1px solid #666699;"|[[Failure]] |
− | |Uses [[GenericOneByteMsg|Generic One Byte Msg]]. | + | |style="border: 1px solid #666699;"|Uses [[GenericOneByteMsg|Generic One Byte Msg]]. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0051 |
− | | | + | |style="border: 1px solid #666699;"|[[Success]] |
− | |Uses [[GenericOneByteMsg|Generic One Byte Msg]]. | + | |style="border: 1px solid #666699;"|Uses [[GenericOneByteMsg|Generic One Byte Msg]]. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0100 |
− | | | + | |style="border: 1px solid #666699;"|[[RemHostNameSET]] |
− | |Uses [[GenericOneStringMsg|Generic One String Msg]]. | + | |style="border: 1px solid #666699;"|Uses [[GenericOneStringMsg|Generic One String Msg]]. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0150 |
− | | | + | |style="border: 1px solid #666699;"|[[DisconnectREQ]] |
− | | "MsgType Only" NetMsg and has no body. | + | |style="border: 1px solid #666699;"|"MsgType Only" NetMsg and has no body. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0200 |
− | | | + | |style="border: 1px solid #666699;"|[[NewHostOnNet]] |
− | |Uses [[GenericOneStringMsg|Generic One String Msg]]. | + | |style="border: 1px solid #666699;"|Uses [[GenericOneStringMsg|Generic One String Msg]]. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0250 |
− | | | + | |style="border: 1px solid #666699;"|[[FullHostListREQ]]* |
− | | '''''Not Implemented Yet''' | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0255 |
− | | | + | |style="border: 1px solid #666699;"|[[FullHostList]]* |
− | | '''''Not Implemented Yet''' | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0300 |
− | | | + | |style="border: 1px solid #666699;"|[[NewSessionREQ]]* |
− | | | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0305 |
− | | | + | |style="border: 1px solid #666699;"|[[NewSession]]* |
− | | | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0310 |
− | | | + | |style="border: 1px solid #666699;"|[[LogoutSession]] |
− | | | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0400 |
− | | | + | |style="border: 1px solid #666699;"|[[GeometryREQ]] |
− | |Uses [[GenericOneStringMsg|Generic One String Msg]] in addition to custom fields. | + | |style="border: 1px solid #666699;"|Uses [[GenericOneStringMsg|Generic One String Msg]] in addition to custom fields. |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0405 |
− | | | + | |style="border: 1px solid #666699;"|[[GeometryMANIFEST]] |
− | | | + | |style="border: 1px solid #666699;"|'''''Not Implemented Yet''' |
|- | |- | ||
− | | | + | |style="border: 1px solid #666699;"|0x0410 |
− | | | + | |style="border: 1px solid #666699;"|[[GeometryCHUNK]] |
− | |Uses [[GenericMultiByteMsg|Generic Multi Byte Msg]]. | + | |style="border: 1px solid #666699;"|Uses [[GenericMultiByteMsg|Generic Multi Byte Msg]]. |
|} | |} |
Revision as of 16:43, 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:
NOTE: This list is not uptodate as of 1.25.11
MsgType ID | 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* | Not Implemented Yet |
0x0305 | NewSession* | Not Implemented Yet |
0x0310 | LogoutSession | Not Implemented Yet |
0x0400 | GeometryREQ | Uses Generic One String Msg in addition to custom fields. |
0x0405 | GeometryMANIFEST | Not Implemented Yet |
0x0410 | GeometryCHUNK | Uses Generic Multi Byte Msg. |