An idle subscription to another session delivers one notice or an expiry, and older peers are refused.
What's wrong with this entry?
A subscription to another session's idle state results in a single [Cross-session idle notice] message, or a notice that the subscription expired. Peers running an older version are reported as unsupported and nothing is subscribed.
- The local socket channel gained request and notice frame types, correlated back to the original message id.
- Self-targets and out-of-reach namespaces are vetted and refused.
- Analytics under
cross_session_notify_idlecover own_inbox_unbound, unvettable_reply_target, self_target_frame, malformed_frame and malformed_notice. - Session records advertise their supported peer features so version mismatches are detected before subscribing.
- The parameter is only present in the cross-session-messaging build of the tool.
notify_when_idle: that session runs a version without idle notices \u2014 nothing was subscribed.
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross