Difference between revisions of "GeometryServiceNetworkProtocol"
From BRL-CAD
(Add in GSnet graphic and align.) |
(Change links to start eliminating the iBME references.) |
||
| Line 43: | Line 43: | ||
|- | |- | ||
|MessageUUID | |MessageUUID | ||
| − | |[[ | + | |[[GSNet_String|String (Variable bytes)]] |
| | | | ||
|- | |- | ||
| Line 51: | Line 51: | ||
|- | |- | ||
|RegardingMessageUUID | |RegardingMessageUUID | ||
| − | |[[ | + | |[[GSNet_String|String (Variable bytes)]] |
| | | | ||
|} | |} | ||
Revision as of 13:09, 18 January 2011
 |
The Geometry Service Network (GSNet) Protocol is a TCP/IP based protocol designed to facilitate socketed communications between Geometry Service Nodes on a network. A Geometry Service Node is defined as any softwares that supports communication via the GSNet Protocol.
|
Visual GSNet Msg Breakdown
GSNet Msg
Header
The header of the GSNet Msg contains the information necessary for quickly determining authenticity, type and length. Geometry Service's network library, libNetwork, is built upon BRL-CAD's networking library: libPKG. This causes the header byte layout to look like this:
| Element | Length | Value |
| Magic1 | int16 (2 Bytes) | Always 0x41FE |
| Magic2 | int16 (2 Bytes) | Always 0x5309 |
| MessageLength | int32 (4 bytes) | |
| MsgType | int16 (2 bytes) | |
| MessageUUID | String (Variable bytes) | |
| HasRegardingUUID | Boolean (1 byte) | |
| RegardingMessageUUID | String (Variable bytes) |
libPKG Part
GSNet Part
Data
List of NetMsgTypes.
List of Common NetMsg Exchanges
