Difference between revisions of "OpenIGTLink/ProtocolV2/Query"
From NAMIC Wiki
| Line 1: | Line 1: | ||
=Simple Querying Mechanism in OpenIGTLink Protocol version 2= | =Simple Querying Mechanism in OpenIGTLink Protocol version 2= | ||
| − | In OpenIGTLink version 2, special prefixes are used in the message type field in the header to query and control data flow. | + | In OpenIGTLink version 2, special prefixes '''GET_''', '''STT_''', '''STP_''', and '''RTS_''' are used in the message type field in the header for messages to query and control data flow. Those messages with those special prefix should be defined along with primary message types (for example, STT_TDATA, STP_TDATA and RTS_TDATA should be defined with TDATA). |
| + | |||
=='''GET_''' prefix: Query a single message== | =='''GET_''' prefix: Query a single message== | ||
=='''STT_''' and '''STP_''' prefixes: Control data flow== | =='''STT_''' and '''STP_''' prefixes: Control data flow== | ||
=='''RTS_''' prefix: Response to get, start and stop messages== | =='''RTS_''' prefix: Response to get, start and stop messages== | ||
| + | |||
=Examples= | =Examples= | ||
Revision as of 15:44, 25 June 2010
Home < OpenIGTLink < ProtocolV2 < QueryContents
Simple Querying Mechanism in OpenIGTLink Protocol version 2
In OpenIGTLink version 2, special prefixes GET_, STT_, STP_, and RTS_ are used in the message type field in the header for messages to query and control data flow. Those messages with those special prefix should be defined along with primary message types (for example, STT_TDATA, STP_TDATA and RTS_TDATA should be defined with TDATA).
