RosIntegration » History » Version 3
J. Wienke, 06/10/2011 05:42 PM
| 1 | 1 | J. Moringen | h1. ROS Integration |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | Potential Strategies: |
| 4 | 1 | J. Moringen | |
| 5 | 1 | J. Moringen | * (Generic) Bridge Component |
| 6 | 1 | J. Moringen | * ROS Port (ROS as a transport, mapping to our concepts) |
| 7 | 1 | J. Moringen | * RSB Integration in ROS |
| 8 | 1 | J. Moringen | |
| 9 | 1 | J. Moringen | Ideas: |
| 10 | 1 | J. Moringen | |
| 11 | 1 | J. Moringen | * Naming maintains features sets (which component understands what on which framework) |
| 12 | 2 | J. Wienke | |
| 13 | 2 | J. Wienke | Experiences: |
| 14 | 2 | J. Wienke | |
| 15 | 2 | J. Wienke | * No grammar for IDL available |
| 16 | 2 | J. Wienke | * XMLRPC nameserver protocol must be implemented by hand |
| 17 | 2 | J. Wienke | ** half specified |
| 18 | 3 | J. Wienke | * Complicated and mandatory state management (subscriber links) |
| 19 | 3 | J. Wienke | ** creates coupling |