ros2 / ros2/rclcpp

intra-process communication with serialized message

Open
#1,710 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
C++
Stars
805
Forks
564
Avg merge
1d 17h
Merged PRs (30d)
27

Description

Hi all,

I'm work on a embedded linux system with 4-core A53 platform, and I'm planning to use ros2 to implement the intra-process communication.

For some reason, I'm not willing to use the default ros msg generation mechanism, but some other IDL language generator (like protobuf, flatsbuffer and so on), so I'd like to pass a serialized message directly to to ros publish function. But then, in the source code, I found the serialized message publish for intra-process is not implemented yet
https://github.com/ros2/rclcpp/blob/master/rclcpp/include/rclcpp/publisher.hpp#L466

So is there any schedule to implement the serialized publish recently? or is there any alternative method to achieve my goal?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the serialized-message publishing code referenced in rclcpp/include/rclcpp/publisher.hpp around line 466. Review how intra-process publishing handles messages and how externally generated serialized messages such as protobuf or FlatBuffers would enter the API. Done means the supported approach or implementation scope for serialized intra-process publishing is clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.