- Fix WASM support using
instant::{Duration, Instant}
instead ofstd::time::{Duration, Instant}
. See PR 179.
- Introduce dynamic stream receive window auto-tuning. While low-resourced deployments maintain the benefit of small buffers, high resource deployments eventually end-up with a window of roughly the bandwidth-delay-product (ideal) and are thus able to use the entire available bandwidth. See PR 176 for performance results and details on the implementation.
- Remove
WindowUpdateMode
. Behavior will always beWindowUpdateMode::OnRead
, thus enabling flow-control and enforcing backpressure. See PR 178.
- Deprecate
WindowUpdateMode::OnReceive
. It does not enforce flow-control, i.e. breaks backpressure. UseWindowUpdateMode::OnRead
instead. See PR #177.
-
Remove
Control
andControlledConnection
. Users have to move to thepoll_
functions ofConnection
. See PR #164. -
Fix a bug where
Stream
s would not be dropped until their correspondingConnection
was dropped. See PR #167.
- Avoid race condition between pending frames and closing stream. See PR 156.
- Remove
Connection::control
in favor ofControl::new
. RemoveConnection::next_stream
in favor ofConnection::poll_next_inbound
. See PR 142.
- Process command or socket result immediately and thereby no longer accessing the socket after it returned an error. See PR 138 for details.
-
Default to
WindowUpdateMode::OnRead
, thus enabling full Yamux flow-control, exercising back pressure on senders, preventing stream resets due to reaching the buffer limit.See the
WindowUpdateMode
documentation for details, especially the section on deadlocking when sending data larger than the receivers window.
-
Force-split larger frames, for better interleaving of reads and writes between different substreams and to avoid single, large writes. By default frames are capped at, and thus split at,
16KiB
, which can be adjusted by a new configuration option, if necessary. -
Send window updates earlier, when half of the window has been consumed, to minimise pauses due to transmission delays, particularly if there is just a single dominant substream.
-
Avoid possible premature stream resets of streams that have been properly closed and already dropped but receive window update or other frames while the remaining buffered frames are still sent out. Incoming frames for unknown streams are now ignored, instead of triggering a stream reset for the remote.
- Avoid possible premature stream resets of streams that have been properly closed and already dropped but receive window update or other frames while the remaining buffered frames are still sent out. Incoming frames for unknown streams are now ignored, instead of triggering a stream reset for the remote.
- Upgrade step 4 of 4. This version always assumes the new semantics and no longer sets the non-standard flag in intial window updates.
- The configuration option
lazy_open
is removed. Initial window updates are sent automatically if the receive window is configured to be larger than the default.
Upgrade step 3 of 4. This version sets the non-standard flag, but irrespective of whether it is present or not, always assumes the new additive semantics of the intial window update.
Upgrade step 2 of 4. This version sets the non-standard flag, version 0.5.0 already recognises.
This version begins the upgrade process spawning multiple versions that changes the meaning of the initial window update from "This is the total size of the receive window." to "This is the size of the receive window in addition to the default size." This is necessary for compatibility with other yamux implementations. See issue #92 for details.
As a first step, version 0.5.0 interprets a non-standard flag to imply the
new meaning. Future versions will set this flag and eventually the new
meaning will always be assumed. Upgrading from the current implemention to
the new semantics requires deployment of every intermediate version, each of
which is only compatible with its immediate predecessor. Alternatively, if
the default configuration together with lazy_open
set to true
is
deployed on all communicating endpoints, one can skip directly to the end
of the transition.
- Bugfixes (#93).
- Bugfixes (#91).
- Improve documentation (#88).
- Bugfix release (#85).
- Send RST frame if the window of a dropped stream is 0 and it is in state
SendClosed
(#84).
- Removed
bytes
(#77) andthiserror
(#78) dependencies. - Removed implicit
BufWriter
creation (#77). Client code that depends on this (undocumented) behaviour needs to wrap the socket in aBufWriter
before passing it toConnection::new
. - Added
Connection::is_closed
flag (#80) to immediately returnOk(None)
fromConnection::next_stream
afterErr(_)
orOk(None)
have been returned previously.
- Control and stream command channels are now closed and drained immediately
on error. This is done to prevent client code from submitting further close
or other commands which will never be acted upon since the API contract of
Connection::next_stream
is that afterNone
or anErr(_)
is returned it must not be called again.
- Updates nohash-hasher dependency to v0.2.0.
- A new configuration option
lazy_open
(off by default) has been added and inbound streams are now acknowledged (#73). Iflazy_open
is set totrue
we will not immediately send an initialWindowUpdate
frame but instead just set theSYN
flag on the first outboundData
frame. SeeConfiguration::set_lazy_open
for details.
- Log connection reset errors on debug level (#72).
- Hide
StreamId::new
and update dependencies.
Update to use and work with async/await:
Config::set_max_pending_frames
has been removed. Internal back-pressure made the setting unnecessary. As another consequence the errorConnectionError::TooManyPendingFrames
has been removed.Connection
no longer has methods to open a new stream or to close the connection. Instead a separate handle typeControl
has been added which allows these operations concurrently to the connection itself.- In Yamux 0.2.x every
StreamHandle
I/O operation would drive theConnection
. Now, the only way theConnection
makes progress is through itsnext_stream
method which must be called continuously. For convenience a functioninto_stream
has been added which turns theConnection
into afutures::stream::Stream
impl, invokingnext_stream
in itspoll_next
method. StreamHandle
has been renamed toStream
and its methodscredit
andstate
have been removed.Stream
also implementsfutures::stream::Stream
and producesPacket
s.ConnectionError::StreamNotFound
has been removed. Incoming frames for unknown streams are answered with a RESET frame, unless they finish the stream.DecodeError
has been renamed toFrameDecodeError
andDecodeError::Type
corresponds toFramedDecodeError::Header
which handles not just unknown frame type errors, but more. Hence a new errorHeaderDecodeError
has been added for those error cases.
- Updated dependencies (#56).
- Bugfix release (pull request #54).
- Added
max_pending_frames
setting toConfig
. AConnection
buffers outgoing frames up to this limit (see pull request #51). - Added
ConnectionError::TooManyPendingFrames
ifmax_pending_frames
has been reached. - Changed error types of
Connection::close
andConnection::flush
fromstd::io::Error
toyamux::ConnectionError
. - Removed
Connection::shutdown
method which was deprecated since version 0.1.8.
- Add
read_after_close
setting toConfig
which defaults totrue
to match the behaviour of previous versions. Settingread_after_close
tofalse
will cause stream reads to return withOk(0)
as soon as the connection is closed, preventing them from reading data from their buffer.
- Mark
Connection::shutdown
as deprecated (#44).
- Bugfix release (#36).
- Support for half-closed streams (#38).
- Avoids redundant RESET frames (#37).
- Better test coverage (#40, #42).
- Bugfix release (pull requests #34 and #35).
- Bugfix release (pull request #33).
- Bugfix release (pull requests #30 and #31).
- Bugfix release (pull requests #27 and #28).
- Bugfix release. See pull request #26 for details.
- Forward
Stream::poll
to the newly addedConnection::poll
method which acceptsself
as a shared reference. See pull request #24 for details.
- Initial release.