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
Describe what you want implemented The Peer API should expose a send method to "broadcast" a message to a specific target.
send
Describe "Why" this is needed This is required to handle a ping/pong paradigm useful in the following scenario Eg:
FindBlock
BlockReady
GetBlock
Block
Describe alternatives you've considered The client caller can broadcast a sort of "Ping" message to the network and handle the multiple response.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Does this function definition seem adequate? @herr-seppia
/// Send a message to a peer in the network. pub async fn send(&self, peer: PeerInfo, message: &[u8])
Sorry, something went wrong.
Does this function definition seem adequate?
Does the client know anything about PeerInfo? Due to the fact this is a prerequisite for #59, maybe a SocketAddr is enough
PeerInfo
SocketAddr
What about this signature?
/// Send a message to a peer in the network. pub async fn send(&self, message: &[u8], target: SocketAddr) {
Successfully merging a pull request may close this issue.
Describe what you want implemented
The Peer API should expose a
send
method to "broadcast" a message to a specific target.Describe "Why" this is needed
This is required to handle a ping/pong paradigm useful in the following scenario
Eg:
FindBlock
messageBlockReady
responsesGetBlock
messageBlock
messageDescribe alternatives you've considered
The client caller can broadcast a sort of "Ping" message to the network and handle the multiple response.
Additional context
Add any other context or screenshots about the feature request here.The text was updated successfully, but these errors were encountered: