Replies: 1 comment 4 replies
-
Hi @harsszegi You might be interested on the |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm using RELIABLE_RELIABILITY_QOS for both publisher and subscriber over WAN + TCPv4. I have an issue. My publisher client code should be a "fire and forget" client, meaning it sends out the message, then it should close the channel if the subscriber has received the message.
When DataWriter's write() returns I suppose the message has been pushed onto the TCP socket, however as I close the socket via closing the writer, publisher, topic, etc., the subscriber is not receiving it.
Obviously If I "wait enough" after doing the write() and before closing the socket everything works just fine.
Is there a QOS or any other solution that I could use for the publisher to make sure that subscriber actually read the message from the socket?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions