Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add QP_LIFESPAN to READER_QOS_MASK #407

Closed
wants to merge 1 commit into from

Conversation

@rotu rotu requested a review from eboasson February 24, 2020 23:10
@rotu
Copy link
Contributor Author

rotu commented Feb 25, 2020

Build failures look spurious.

@eboasson
Copy link
Contributor

Thanks @rotu , but there are some issues with this PR:

  • The first is that this while adds a "lifespan" QoS setting on the reader, it doesn't actually implement any behaviour.
  • The second is that the absence of "lifespan" on the reader is deliberate: in DDS, it is a QoS of the writer (see, e.g., page 2-110 of the DCPS 1.4 spec). There is certainly a reasonable argument in favour of adding a "reader lifespan", but there are also reasonable arguments why it doesn't make sense to do that.

In my view the real issue is that "get_publishers_subscriptions_info_by_topic" incorrectly tests whether one can set/get lifespan on a reader. In rcl that got fixed by ros2/rcl#571

After due deliberation it might turn out that adding a lifespan QoS on the reader is a worthwhile exercise, but that's a separate matter.

@rotu
Copy link
Contributor Author

rotu commented Feb 25, 2020

Thanks, @eboasson! Superceeded by ros2/rclcpp#1002

@rotu rotu closed this Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants