IronRDP/crates/ironrdp-blocking
Benoît Cortier c21fa44fd6
build: do not use workspace dependencies (#695)
As written in the workspace Cargo.toml:

> Note that for better cross-tooling interactions, do not use workspace
dependencies for anything that is not "workspace internal" (e.g.: mostly
dev-dependencies). E.g.: release-plz can’t detect that a dependency has
been
updated in a way warranting a version bump in the dependant if no commit
is
touching a file associated to the crate. It is technically okay to use
that
for "private" (i.e.: not used in the public API) dependencies too, but
we
still want to make follow-up releases to stay up to date with the
community,
even for private dependencies.

Expectation is that release-plz will be able to auto-detect when bumping
dependents is necessary.

Closes #689
2025-03-12 09:25:01 -04:00
..
src fix(server): drop unexpected PDUs during deactivation-reactivation 2025-01-27 07:35:36 -05:00
Cargo.toml build: do not use workspace dependencies (#695) 2025-03-12 09:25:01 -04:00
CHANGELOG.md chore(release): prepare for publishing (#628) 2025-01-28 23:24:35 +00:00
LICENSE-APACHE chore: symlinks to license files in packages (#604) 2024-12-11 08:13:26 -05:00
LICENSE-MIT chore: symlinks to license files in packages (#604) 2024-12-11 08:13:26 -05:00
README.md docs: add project links to READMEs for consistency 2024-10-29 19:14:20 +09:00

IronRDP Blocking

Blocking I/O abstraction wrapping the IronRDP state machines conveniently.

This crate is a higher level abstraction for IronRDP state machines using blocking I/O instead of asynchronous I/O. This results in a simpler API with fewer dependencies that may be used instead of ironrdp-async when concurrency is not a requirement.

This crate is part of the IronRDP project.