Skip to content

Clarification around RTL16a client-side behaviour #44

@QuintinWillison

Description

@QuintinWillison

Issue created in response to this review comment in our JavaScript client library.

We need to make sure that when the client sends a new attach message in order to set options that the local state machine for that channel doesn't incorrectly transition in to an attaching state as a side-effect, but instead remains in its current state (which will either be attaching or attached as specified in RTL16a).

┆Issue is synchronized with this Jira Task by Unito

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions