|
|
| (11 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | =Title=
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer/Features/Middleware here]</font></big> |
| − | Middleware
| |
| − | | |
| − | =Names=
| |
| − | *session leader
| |
| − | | |
| − | *participants
| |
| − | | |
| − | =Technology/Function description=
| |
| − | * Publish subscribe ORB/ACE [Peter]
| |
| − | * Socket IGSTK [Junichi Patrick]
| |
| − | | |
| − | Requirements
| |
| − | * Reliable for command transfer (all data transferred, in order)
| |
| − | * Fast for tracking data transfer (only the latest coordinate is required, can lose data)
| |
| − | * Image transfer (500K or more)
| |
| − | * Data types (struct: string, integer, float)
| |
| − | * Data type checking (number is correctly formatted etc)
| |
| − | * Time out (device is down)
| |
| − | | |
| − | Would be nice to have
| |
| − | * Priority
| |
| − | * Point - multi-point data transfer
| |
| − | | |
| − | Question
| |
| − | * UDP - fast, no delay due to ACK packages
| |
| − | * TCP/IP - reliable, easy
| |
| − | * Security
| |
| − | ** malicious packets or sent by mistake
| |
| − | ** CRC and auth.?
| |
| − | ** pop up a dialog box before accepting data? (just one, to avoid flood)
| |
| − | ** same issues with [[Slicer3:Slicer_Daemon]]
| |
| − | | |
| − | See: [http://www.cisst.org/wiki/MRI_robot/MIT_2007_06_27_Meeting discussion about data transfer]
| |
| − | | |
| − | =Potential application in IGT=
| |
| − | * Tracker data transfer
| |
| − | * Image transfer from MRI
| |
| − | * Robot coordinate transfer
| |
| − | * Robot control
| |
| − | * Periferials: OpenTracker/Navitrack has 3D mouse driver etc.
| |
| − | | |
| − | =Which part is already in Slicer=
| |
| − | | |
| − | =What is not=
| |
| − | | |
| − | =Who among us will take leading role?=
| |
| − | | |
| − | =Links=
| |
