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
NettyServer uses UnicastProcessor as a publisher of incoming connections. Thus it supports one subscriber only. This is a problem, if one wants to implement beaconchain_peers metric, for example. As a part of metrics implementation (#178), I temporarily attached ReplayProcessor to UnicastProcessor, and used former as channels stream (by analogy to ConnectionManager client connections stream).
While it's working, the implementation should be rewised.
The text was updated successfully, but these errors were encountered:
NettyServer uses UnicastProcessor as a publisher of incoming connections. Thus it supports one subscriber only. This is a problem, if one wants to implement beaconchain_peers metric, for example. As a part of metrics implementation (#178), I temporarily attached ReplayProcessor to UnicastProcessor, and used former as channels stream (by analogy to ConnectionManager client connections stream).
While it's working, the implementation should be rewised.
The text was updated successfully, but these errors were encountered: