Support matched/unmatched event#101
Conversation
fujitatomoya
left a comment
There was a problem hiding this comment.
overall looks good to me.
|
@asorbini we would like to request another review on this. Related to new feature, ros2/rmw#330 (comment) |
|
@asorbini could you take a look at this? |
| { | ||
| this->status_matched = *status; | ||
|
|
||
| if (status->current_count_change == 1) { |
There was a problem hiding this comment.
current_count_change will be either 1 or -1 always? otherwise, we will miss the event. as far as i see the specification, this could be 2 or -2 for example.
There was a problem hiding this comment.
I think the processing likes Fastdds.
@asorbini please help to confirm this since I have no source codes.
|
@Barry-Xu-2018 this has some conflicts now. |
|
Thanks for notification.
Yes. I found it and fix it now. |
|
Now interface is changed. We only use matched event in rmw layer (ros2/rmw#331). |
Signed-off-by: Barry Xu <barry.xu@sony.com>
12de24e to
4a94ebc
Compare
|
@asorbini friendly ping, we would like you to review on this one. |
Address ros2/rmw#330