Buffered Realtime Publisher

[mamueluth]

Is your feature request related to a problem? Please describe.
In the current implementation of the RealtimePublisher we use the try_publish(msg) function for publishing. This function is non-blocking but it does give no guarantee that the msg will actually be published.

We could check the return value and if an try again, however this lays responsibility on the user of the RealtimePublisher to wait and retry or buffer and retry later. I would like to have a version of the RealtimePublisher where you can enqueue a message and it will be published at the next possible time.

Describe the solution you'd like
A possible sollution would be a version of the RealtimePublisher which can enqueue messages and published them.

Describe alternatives you've considered
I would like to discuss this approach and alternative approaches are welcome.

[saikishor]

Yess, this is exactly what I wanted to add. That's one reason to have the msg variable non public and add other methods, so we can open the possibility to this.

We can use the LockFreeQueue that we have in this repo or use the circular buffer of boost for this approach?. One thing that needs to be done before this is to have the possibility to define the publisher directly and there we can add a possibility of a queue size?.

What do you think?

[christophfroehlich]

Isn't this exactly the direction of #461? @bjin2364

[saikishor]

Isn't this exactly the direction of #461? @bjin2364

Truee

[mamueluth]

Yes sorry overlooked it:) Will give the other a review

[saikishor]

Yes sorry overlooked it:) Will give the other a review

@mamueluth that doesn't contain the complete changes

[christophfroehlich]

should we change the existing class, or add a new one?

[saikishor]

should we change the existing class, or add a new one?

I think this can fit into the existing class

[christophfroehlich]

@bjin2364 what do you think?

should we change the existing class, or add a new one?

I think this can fit into the existing class

[github-actions]

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

[github-actions]

This issue was closed because it has been stalled for 45 days with no activity.