A reconnecting client can pick up events the previous connection never received.
What's wrong with this entry?
The session client gains ways to take, discard or adopt events that never reached the client, so a new connection can pick up where a closed one left off. Events marked ephemeral are always filtered out.
- New calls: take, discard and adopt undelivered client events.
- The remote bridge now explicitly discards undelivered events when its v2 connection closes rather than dropping them silently.
discardUndeliveredEvents
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
Streaming read index no longer skips messages
Both mention transport
-
v2.1.225
Unknown control messages complete their command lifecycle
Both mention transport
-
v2.1.234
The stdin transport now answers the remote-transport questions
Both mention transport