Skip to content
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 4.3 Protocol and rediscovery the Routing Table using the Route Message #646

Merged
merged 21 commits into from
Dec 8, 2020

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Dec 3, 2020

Starting the development of the version 4.3 with the creation of the protocol class making it available on the handshake. The replacement of the routing procedure by the route message for routing table discovery on this new version pushes the complexity to the server and makes the protocol cleaner and more efficient.

The routing table requisition details was pushed to the protocol implementation classes, the request provides a observer which parses the response and make it available as a RawRoutingTable on completed.

The rediscovery class uses the method, constructs the RoutingTable and treats the exceptional cases.

@bigmontz bigmontz force-pushed the 4.3-routing-message branch from e39e9aa to 0dd1232 Compare December 7, 2020 16:26
@bigmontz bigmontz force-pushed the 4.3-routing-message branch from 0dd1232 to 6700596 Compare December 8, 2020 09:12
@bigmontz bigmontz merged commit 9894a29 into neo4j:4.3 Dec 8, 2020
@bigmontz bigmontz deleted the 4.3-routing-message branch December 8, 2020 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants