You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2019. It is now read-only.
Hi, I am using the tacopie server to handle a server internal to my application (a recovery server) and want to send a lot of messages. But the problem i see is immediately after all the async_writes the connection gets terminated even without checking if all the messages were successfully written onto the socket. Is there any way to confirm the same or at least wait till all the messages are flushed onto the socket.
Thanks,
Siril.
The text was updated successfully, but these errors were encountered:
I have resolved the issue by directly sending out the message on the tcp_socket of the client. However would be nice to know if there is a way to force the async_write to flush all the data onto the socket.
Hi, I am using the tacopie server to handle a server internal to my application (a recovery server) and want to send a lot of messages. But the problem i see is immediately after all the async_writes the connection gets terminated even without checking if all the messages were successfully written onto the socket. Is there any way to confirm the same or at least wait till all the messages are flushed onto the socket.
Thanks,
Siril.
The text was updated successfully, but these errors were encountered: