Difference between revisions of "Slicer/Features/Middleware"
From NAMIC Wiki
| Line 38: | Line 38: | ||
** pop up a dialog box before accepting data? (just one, to avoid flood) | ** pop up a dialog box before accepting data? (just one, to avoid flood) | ||
** same issues with [[Slicer3:Slicer_Daemon]] | ** same issues with [[Slicer3:Slicer_Daemon]] | ||
| + | * Firewall? | ||
==See also== | ==See also== | ||
| Line 48: | Line 49: | ||
* Robot control | * Robot control | ||
* Periferials: OpenTracker/Navitrack has 3D mouse driver etc. | * Periferials: OpenTracker/Navitrack has 3D mouse driver etc. | ||
| + | |||
=Which part is already in Slicer= | =Which part is already in Slicer= | ||
Revision as of 16:44, 14 December 2007
Home < Slicer < Features < MiddlewareContents
Title
Middleware
Names
- session leader
- participants
Technology/Function description
Goal
- Slicer + IGSTK
Technologies
- Look at Publish subscribe ORB/ACE - DDS [Peter]
- Socket IGSTK [Junichi Patrick]
- Navitrack - phase out?
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
Questions
- 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
- Firewall?
See also
Potential application in IGT
- Tracker data transfer
- Image transfer from MRI
- Robot coordinate transfer
- Robot control
- Periferials: OpenTracker/Navitrack has 3D mouse driver etc.
