Add high-level boundary management interface #2177
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beryll1um
force-pushed
the
dev-router-boundary-management
branch
2 times, most recently
from
0d7c3e6 to
b611205
Compare
Author
|
Still working on some minor improvements and bug fixes. I think this change requires better logging for closing outbound, but not all outbound implementations have a close method, which makes it a bit messy, so maybe we'll have to do the same thing we do on inbound to unify the outbound close interface and put the close log there. |
Author
|
See examples in #2180! |
beryll1um
force-pushed
the
dev-router-boundary-management
branch
from
b611205 to
c945858
Compare
Author
|
Revised few boundary mutex read lock places, and improved the structure of the Router interface and implementation. |
beryll1um
force-pushed
the
dev-router-boundary-management
branch
from
c945858 to
f25cb7c
Compare
I rewrote the router's boundary management part to implement dynamic management from a high-level box interface. This also includes a number of changes I made in the process of rewriting some messy parts, such as the Outbound tree bottom-top starter.
beryll1um
force-pushed
the
dev-router-boundary-management
branch
from
f25cb7c to
99840ba
Compare
nekohasekai
force-pushed
the
dev-next
branch
7 times, most recently
from
ac6c4b0 to
6740910
Compare
nekohasekai
force-pushed
the
dev-next
branch
5 times, most recently
from
81dc9e7 to
d6597fa
Compare
nekohasekai
force-pushed
the
dev-next
branch
2 times, most recently
from
58913be to
b148629
Compare
nekohasekai
force-pushed
the
dev-next
branch
3 times, most recently
from
c689437 to
84ceb90
Compare
nekohasekai
force-pushed
the
dev-next
branch
from
87eb193 to
877e7a8
Compare
nekohasekai
force-pushed
the
dev-next
branch
10 times, most recently
from
b83776e to
b424757
Compare
nekohasekai
force-pushed
the
dev-next
branch
15 times, most recently
from
553c5b5 to
16ad84c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I rewrote the router's boundary management part to implement dynamic management from a high-level box interface. This also includes a number of changes I made in the process of rewriting some messy parts, such as the Outbound tree bottom-top starter.
What I reallly need is someone how is experianced in this project (like @nekohasekai) to check my changes and verify everything good and I didn't forget anything. I'm planning to run my project on it, so wait for more improvements in the future =)