Difference between revisions of "GeometryCHUNK"

From BRL-CAD
(Description)
(Description)
Line 4: Line 4:
 
[[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.
 
[[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.
  
If a [[GeometryREQFAIL]] message is displayed, this indicates that the GeometryCHUNK has failed. <BSRJ>
+
If a [[GeometryREQFAIL]] message is displayed, this indicates that the GeometryCHUNK object has failed. <BSRJ>
  
 
==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 13:54, 30 December 2012

Design icon.png 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.

If a GeometryREQFAIL message is displayed, this indicates that the GeometryCHUNK object has failed. <BSRJ>

Byte Format

No additional fields beyond that of the Common Header and GenericMultiByteMsg