Crate gnostr_cat

source ·
Expand description

Note: library usage is not semver/API-stable

Type evolution of a websocat run:

  1. &str - string as passed to command line. When it meets the list of SpecifierClasses, there appears:
  2. SpecifierStack - specifier class, final string argument and vector of overlays.
  3. Specifier - more rigid version of SpecifierStack, with everything parsable parsed. May be nested. When construct is called, we get:
  4. PeerConstructor - a future or stream that returns one or more connections. After completion, we get one or more of:
  5. Peer - an active connection. Once we have two of them, we can start a:
  6. Session with two Transfers - forward and reverse.

Re-exports§

Modules§

Macros§

Structs§

  • Some information passed from the left specifier Peer to the right
  • First representation of websocat command-line, partially parsed.
  • Second representation of websocat configuration: everything (e.g. socket addresses) should already be parsed and verified A structural form: two chains of specifier nodes. Futures/async is not yet involved at this stage, but everything should be checked and ready to do to start it (apart from OS errors)
  • An immutable chain of functions that results in a Futures or Streams that rely on each other. This is somewhat like a frozen form of WebsocatConfiguration2.

Enums§

Functions§

Type Aliases§