Skip to content

feat: improved client close #53

@robertsLando

Description

@robertsLando

@robertsLando

Also I don't know if there is a way to make store async as well and actually make it return when the transport is gracefully closed

@jacoscaz
We likely need the transport to emit a close event and listen to that from the client, which can then call its own close() method. If so, I think this would fall within the scope of a separate PR as it needs some work on transports first.

Originally posted by @jacoscaz in #52 (comment)

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