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
This discussion was converted from issue #208 on July 05, 2023 18:50.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Related to the resumable sessions feature (v1.4).
Right now, if session has been restored, we do not notify a Ruby app about it. So, the lifecycle looks as follows:
So, we're not only missing the "connect" (or "restore") event, but also we may have two "disconnect" events.
It seems that we need to add a new RPC method (Restore?) and also trigger connection/channel class callbacks (
reconnect
andresubscribed
?).What are the other options? Postpone
Disconnect
calls till the session cache expired—not good, the TTL can be minutes—too long.Beta Was this translation helpful? Give feedback.
All reactions