Difference between revisions of "OpenIGTLink/Approaches"
From NAMIC Wiki
| Line 2: | Line 2: | ||
===Implement by yourself=== | ===Implement by yourself=== | ||
*Writing applications in non-C or C++ language | *Writing applications in non-C or C++ language | ||
| − | *The protocol is defined in [[OpenIGTLink/Protocol | the protocol description page]] | + | *The protocol is defined in [[OpenIGTLink/Protocol | the protocol description page]]. |
===Use simple C code=== | ===Use simple C code=== | ||
| Line 14: | Line 14: | ||
**TCP/IP Socket | **TCP/IP Socket | ||
**Thread and Mutex useful to make server program | **Thread and Mutex useful to make server program | ||
| + | **The library instruction is available in [[OpenIGTLink/Library | the Open IGT Link Library page]]. | ||
Revision as of 14:13, 25 June 2008
Home < OpenIGTLink < ApproachesContents
Three Approaches to Implement Open IGT Link in Your Application
Implement by yourself
- Writing applications in non-C or C++ language
- The protocol is defined in the protocol description page.
Use simple C code
- The code provides C structures for the generic header, image header and transform header, and supporting functions to create a message packet.
- Suitable for applications written in C and C++
- You can just copy the files into your source directory. You never have library link issue.
Use the Open IGT Link Library
- The library supports
- Classes to create Open IGT Link message
- TCP/IP Socket
- Thread and Mutex useful to make server program
- The library instruction is available in the Open IGT Link Library page.
