[ros-users] Making message transport more modular?

Top Page
Attachments:
Message as email
+ (text/plain)
+ (text/html)
Delete this message
Reply to this message
Author: User discussions
Date:  
To: User discussions
Subject: [ros-users] Making message transport more modular?
Hi all,

I'd like to float the following idea: I was wondering if there is some
interest in making ROS transport layer more modular (or maybe just
improving the documentation on the current modularity and integration with
the XMLRPC...).

The rationale behind this idea is two-fold:

- first, to make it easier to address the recurring questions about ROS not
having transport X (replace X with shared memory, multicasting, morse code,
land mail, ... ) or even using an other middleware for transport.

- second, some companies have very good transport layers addressing issues
such as real-time, quality of service, different medium,... but without the
ecosystem of apps in ROS. It could be nice to offer a way to integrate
these features. Maybe there is a link between this questions and moving
towards an enterprise version of ROS.

I'm not going to be pushy about these features, but I would be happy to
contribute or coordinate a SIG if there is enough interest (and support
from WG).

--

Cedric