We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm wondering why you use sync write operation in publishing?
https://github.com/crossbario/autobahn-cpp/blob/master/autobahn/wamp_rawsocket_transport.ipp#L153
The reason I ask is that we get into a problem that our only thread is stuck on this sync write operation around sleep time.
The text was updated successfully, but these errors were encountered:
we could easily have an user option to do writes async (PRs welcome;) (https://www.boost.org/doc/libs/1_67_0/doc/html/boost_asio/reference/async_write.html)
I guess there will be scenarios (many small messages) where it (async write) might have a performance impact. so IMO it should be an option.
Sorry, something went wrong.
Bonefish is doing the same thing....
https://github.com/tplgy/bonefish/blob/master/src/bonefish/rawsocket/tcp_connection.hpp#L78
This really isn't good.
No branches or pull requests
I'm wondering why you use sync write operation in publishing?
https://github.com/crossbario/autobahn-cpp/blob/master/autobahn/wamp_rawsocket_transport.ipp#L153
The reason I ask is that we get into a problem that our only thread is stuck on this sync write operation around sleep time.
The text was updated successfully, but these errors were encountered: