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 Apr 22, 2024. It is now read-only.
The relcast group concept seems badly overloaded by trying to make it general enough to support relcast messaging.
While we would still like for relcast to use libp2p as at least an optional transport, it would be best to move the group management and reconnection logic into a supervisor in the relcast application.
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.
The relcast group concept seems badly overloaded by trying to make it general enough to support relcast messaging.
While we would still like for relcast to use libp2p as at least an optional transport, it would be best to move the group management and reconnection logic into a supervisor in the relcast application.
The text was updated successfully, but these errors were encountered: