-
Notifications
You must be signed in to change notification settings - Fork 690
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
Remove NetworkService::write_notification #551
Comments
We also make heavy use of this API in Polkadot at the moment, so that is also a blocker for removal. |
Polkadot should actually not be that difficult because its code is very asynchronous. The When it comes to GrandPa, however, we still use manual polling, and replacing a synchronous function call with an asynchronous call can require a big amount of refactoring. |
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
Yep, still very important. |
The API of the
write_notification
method doesn't permit back-pressure to be propagated to the code that emits notifications.For this reason,
NetworkService
now has a replacementnotification_sender
method.The
write_notification
isn't marked as#[deprecated]
because we have a policy against that, but it should very much be considered as deprecated.This issue consists in removing the usage of
write_notification
from thesc-network-gossip
crate (the only crate that uses it).It is unclear to me how difficult it is to do so, but I know that it is certainly not trivial.
The text was updated successfully, but these errors were encountered: