[ros-users] Making message transport more modular?

[Jeff Rousseau <jrousseau@aptima.com>]

Having a ROS Transport SIG would be great.  Discussions of various transports have come up now and again on the multi-master SIG list which I think conflates the two topics.  Each (multi-robot/multi-master and transports), although often related, should really be addressed separately.

From: ros-users-bounces at code.ros.org [mailto:ros-users-bounces at code.ros.org] On Behalf Of Cedric Pradalier
Sent: Wednesday, May 23, 2012 3:53 AM
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



The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20120523/503f697f/attachment-0004.html>