Open weboko opened 1 month ago
@danisharora099 would be happy to hear your opinion on the approach
@danisharora099 would be happy to hear your opinion on the approach
Thanks for documenting @weboko.
I'd see these two cases under the same umbrella, as application is not aware if it's a peer disconnection or an internet connection loss -- both of them need to be inferred by recurring Filter pings failing:
ConnectionManager
) as it means that there are no available Filter connect--
PS: perhaps the online/offline state in ConnectionManager
can be extended to be per protocol instead.
@weboko I see this is in progress. I'm curious of how this will be actioned. Can you help share your POV to this? To me it looks like a followup after #2002 is implemented, where we have access to the state of peers used by each protocol, and in this case Filter.
redial peers to which subscription was created; ping and if fails - try to create a new one;
Note: the Filter pings and renewals is a part of https://github.com/waku-org/js-waku/issues/2002. The scope of this issue is solving for js-waku's disconnection