Skip to content

Allow responding to SessionRequests over more than one update #56

@aecsocket

Description

@aecsocket

When you get a SessionRequest, you shouldn't be forced to respond to it in the same update like you have to now. Users should be given a chance to take that request, do some processing (e.g. talk to an auth server), then reply with a response later.

Perhaps an impl Drop which panics, and a fn accept(self) / fn reject(self) which don't panic? So the user isn't allowed to just ignore the request, but they can store it and process it later. Linear types would help a lot here...

Originally raised by a user on Discord

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions