Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
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
Create socket with provided executor #909
Create socket with provided executor #909
Changes from 7 commits
0600c1d
65f76dc
e677e41
b249840
7698f36
6b5ab76
3bb1a81
db2dcc4
abab173
426a024
fea909b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the purpose for the changes here and for passing the local endpoint as a parameter to the
socket_executor_fn_
? (this local endpoint parameter is not used by any of ship/http/p2p)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it might be useful. If someone was wanting to choose which executor according to which endpoint. I'm happy to remove it since we don't have a current use-case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that the socket is always being created with a strand (both here and via the listener), that should mean that all the
bind_executor
s to thestrand
can be removed. Not sure you want to tackle that now or not (going in to 1.0 probably not, but going in to main maybe)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left it mainly because it was targeting 1.0. At this point, maybe it would be cleaner. In many places you would have
boost::asio::post(socket.get_executor(), [](){})
instead which is not really any difference I don't think.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You would have to move the timers to using the strand too (afaict not a problem) but after that it does seem like all 5
bind_executor
s could be removed. I am not seeing the need forboost::asio::post(socket.get_executor(), [](){})
in those same spots. Anyways, it's not something that needs to be done now just a clean up I noticed since we're constructing these more idiomaticly now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, you were talking specifically about the
bind_executor
. I was thinking of theboost::asio::post(strand,
.