Note: library usage is not semver/API-stable
Type evolution of a websocat run:
&str- string as passed to command line. When it meets the list of
SpecifierClasses, there appears:
SpecifierStack- specifier class, final string argument and vector of overlays.
Specifier- more rigid version of SpecifierStack, with everything parsable parsed. May be nested. When
constructis called, we get:
PeerConstructor- a future or stream that returns one or more connections. After completion, we get one or more of:
Peer- an active connection. Once we have two of them, we can start a:
Transfers - forward and reverse.
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 fucntions that results in a
A remnant of the hack
Resolves if/when TCP socket gets reset