-
Notifications
You must be signed in to change notification settings - Fork 186
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
Add Function to Enable Application Layer to Send Direct Control Messages #561
Comments
In principle this is fine, as it can allow application specific extensions to the protocol; this is useful for testing and early adoption as a path to standarization. However, i think that just sending control messages is insufficient. We also need a way to process incoming custom control messages. |
Thanks, I'll then proceed with the PR.
I believe processing incoming messages has already been implemented through the RPC inspector set by the application layer, as shown in this link: #509. Are you considering a different functionality? |
Oh right, i forgot! |
Created the PR: #562 |
ah sorry, i forgot! |
Is it possible to have a tagged release of the |
sure, will make a patch release. |
Description
Proposal: Introduce a new function,
SendControl
, to theGossipSubRouter
that allows the application layer to send direct control messages to a peer. This feature will primarily be used to develop finer-grained testing. Flow blockchain currently uses this feature quite extensively.Proposed Function
Sample implementation on my forked version.
Rationale
Adding this function does not break encapsulation drastically. It is available at the router-level, meaning it is only accessible if the application layer creates a router and passes it to a pubsub instance, rather than creating a gossipsub instance directly. This ensures controlled usage and maintains the integrity of the encapsulation.
Benefits
I can make the PR upon a soft approval.
The text was updated successfully, but these errors were encountered: