Difference between revisions of "GeometryCHUNK"
From BRL-CAD
(Added links to Generics) |
(Clarified field usage.) |
||
| Line 2: | Line 2: | ||
==Description== | ==Description== | ||
| − | [[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains a single serialized Geometry object. Extends [[GenericMultiByteMsg]] (thus contains those fields also). | + | [[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains a single serialized Geometry object. Extends [[GenericMultiByteMsg]] (thus contains those fields also). The String field from [[GenericMultiByteMsg]] is used as the Data field. |
==Byte Format== | ==Byte Format== | ||
No additional fields beyond that of the [[NetMsgTypes|Common Header]] and [[GenericMultiByteMsg]] | No additional fields beyond that of the [[NetMsgTypes|Common Header]] and [[GenericMultiByteMsg]] | ||
Revision as of 14:02, 25 November 2009
|
This page contains the design document for an enhancement or feature. The design should be considered a work in progress and may not represent the final design. As this is a collaborative design, contributions and participation from other developers and users is encouraged. Use the discussion page for providing comments and suggestions. |
Description
NetMsg that contains a single serialized Geometry object. Extends GenericMultiByteMsg (thus contains those fields also). The String field from GenericMultiByteMsg is used as the Data field.
Byte Format
No additional fields beyond that of the Common Header and GenericMultiByteMsg
