Difference between revisions of "OpenIGTLink/Library/Discussions"
From NAMIC Wiki
| Line 21: | Line 21: | ||
==Architecture== | ==Architecture== | ||
| − | * 1 | + | * 1 connection / port |
** needs threading | ** needs threading | ||
** implemented in the OpenIGTLink library | ** implemented in the OpenIGTLink library | ||
| − | * | + | * multiple connection port |
** use 'select()' function | ** use 'select()' function | ||
** not implemented in the OpenIGTLink library | ** not implemented in the OpenIGTLink library | ||
Revision as of 12:19, 7 October 2008
Home < OpenIGTLink < Library < DiscussionsDiscussions on Open IGT Link Library Development
Log function
Data file format
- binary (dump message data to file)
- pro
- can be used for any type of data
- easy to replay
- con
- too redundant, if the data source does not change
- needs reader software
- pro
- text format
- pro
- human readable
- con
- size
- needs interpreter. impossible to record unknown type message.
- pro
Architecture
- 1 connection / port
- needs threading
- implemented in the OpenIGTLink library
- multiple connection port
- use 'select()' function
- not implemented in the OpenIGTLink library
- can be implemented as a single-thread program
Logistics
- Make a copy repository of OpenIGTLink library
- Make wiki account and SVN repository account for the student
Skills required
- Basic knowledge about [OpenIGTLink | OpenIGTLink].
- Socket programming
- Thread
- SVN, CMake
