Difference between revisions of "GeometryREQ"
From BRL-CAD
(Added link to Generic) |
(Clarified field usage.) |
||
| Line 2: | Line 2: | ||
==Description== | ==Description== | ||
| − | [[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains either a UUID or string Path that references a piece of Geometry. Extends [[GenericOneStringMsg]] (thus contains those fields also). | + | [[IBME_GeometryService#NetMsg_Class|NetMsg]] that contains either a UUID or string Path that references a piece of Geometry. Extends [[GenericOneStringMsg]] (thus contains those fields also). The String field from [[GenericOneStringMsg]] is used as the UUID or Path field, depending on the Request Type. |
==Byte Format== | ==Byte Format== | ||
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 either a UUID or string Path that references a piece of Geometry. Extends GenericOneStringMsg (thus contains those fields also). The String field from GenericOneStringMsg is used as the UUID or Path field, depending on the Request Type.
Byte Format
| Element | Length |
| RequestType | byte (1 byte) |
Request Types
| RequestType | Description |
| 0 | The Data is a UUID for the Geometry requested. |
| 1 | The Data is a path to the Geometry requested. |
