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 Sep 26, 2023. It is now read-only.
I'm curious as to why you chose to use UDP as opposed to TCP.
For example instead of having a FIND_SUCCESSOR and FOUND_SUCCESSOR message types, couldn't you just open a TCP connection, request the successor, and then get a response with that information?
I'm honestly not that knowledgeable in this area, and would be interested to know if there is a specific reason TCP might not be as good a solution to use with Chord.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm curious as to why you chose to use UDP as opposed to TCP.
For example instead of having a FIND_SUCCESSOR and FOUND_SUCCESSOR message types, couldn't you just open a TCP connection, request the successor, and then get a response with that information?
I'm honestly not that knowledgeable in this area, and would be interested to know if there is a specific reason TCP might not be as good a solution to use with Chord.
The text was updated successfully, but these errors were encountered: