Two sessions wanting the same name now resolve through fixed outcomes deciding who keeps or yields it.
Session name-claim outcomes are built out but availability is set by remote config.
What's wrong with this entry?
Claiming a session name now resolves to one of a fixed set of outcomes ("own-name", "held", "yielded", "kept", "superseded", "pre-decided"), and that outcome decides whether the name is recorded as user-chosen, auto-generated or a collision, whether the session announces that it gave the name up, and whether the old name is kept for the session list. Part of the cross-session naming machinery, whose availability is set by remote config.
pre-decided
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