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
* Remove redundant sendDelayedEventAction
We do already have the state `hasMemberEvent` that allows to distinguish the two cases. No need to create two dedicated actions.
* fix missing return
* Make membership manager an event emitter to inform about status updates.
- deprecate isJoined (replaced by isActivated)
- move Interface types to types.ts
* add tests for status updates.
* lint
* test "reschedules delayed leave event" in case the delayed event gets canceled
* review
* fix types
* prettier
* fix legacy membership manager
* remove deprecated jitter.
* use non deprecated config fields (keep deprecated fields as fallback)
* update tests to test non deprecated names
* make local NewMembershipManager variable names consistent with config
* make LegacyMembershipManger local variables consistent with config
* comments and rename `networkErrorLocalRetryMs` -> `networkErrorRetryMs`
* review
* This value does not have an effect on the value of `SessionMembershipData.expires`.
93
101
*/
102
+
membershipEventExpiryHeadroomMs?: number;
103
+
/** @deprecated renamed to `membershipEventExpiryHeadroomMs`*/
94
104
membershipExpiryTimeoutHeadroom?: number;
95
105
96
-
/**
97
-
* The period (in milliseconds) with which we check that our membership event still exists on the
98
-
* server. If it is not found we create it again.
99
-
*/
100
-
memberEventCheckPeriod?: number;
101
-
102
-
/**
103
-
* The minimum delay (in milliseconds) after which we will retry sending the membership event if it
104
-
* failed to send.
105
-
*/
106
-
callMemberEventRetryDelayMinimum?: number;
107
-
108
106
/**
109
107
* The timeout (in milliseconds) with which the deleayed leave event on the server is configured.
110
108
* After this time the server will set the event to the disconnected stat if it has not received a keep-alive from the client.
111
109
*/
110
+
delayedLeaveEventDelayMs?: number;
111
+
/** @deprecated renamed to `delayedLeaveEventDelayMs`*/
112
112
membershipServerSideExpiryTimeout?: number;
113
113
114
114
/**
115
115
* The interval (in milliseconds) in which the client will send membership keep-alives to the server.
116
116
*/
117
+
delayedLeaveEventRestartMs?: number;
118
+
/** @deprecated renamed to `delayedLeaveEventRestartMs`*/
117
119
membershipKeepAlivePeriod?: number;
118
120
119
-
/**
120
-
* @deprecated It should be possible to make it stable without this.
121
-
*/
122
-
callMemberEventRetryJitter?: number;
123
-
124
121
/**
125
122
* The maximum number of retries that the manager will do for delayed event sending/updating and state event sending when a server rate limit has been hit.
0 commit comments