Skip to content

Requests: no way to tell an exhausted relay from a silent one #704

Description

@nogringo

NdkResponse gives the events but not what each relay did with the request.
A client cannot tell these three apart:

  • the relay sent EOSE and has nothing more to give,
  • the relay never answered and the request timed out,
  • the request was never sent, because no socket was open.

Proposal: expose the per relay outcome on NdkResponse, for instance

/// Resolves with the outcome of the request on each relay it was sent to.
Future<Map<String, RelayRequestOutcome>> get relayOutcomes;

enum RelayRequestOutcome { eose, closed, timedOut, notSent }

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions