tigrcorn-quic-cc
Versioned congestion-controller contracts and provider discovery for Tigrcorn QUIC transports.
Install
pip install tigrcorn-quic-cc
What It Owns
This dependency-light package owns the public QUIC congestion-control API, immutable event and decision models, entry-point discovery, validation, and provider compliance helpers. It does not own sockets, packet encoding, loss detection, retransmission, flow control, pacing enforcement, or wire ordering.
Use It When
Use this package when authoring a standalone Tigrcorn congestion-control provider or embedding a provider factory into a controlled QUIC integration.
Import Surface
import tigrcorn_quic_cc
print(tigrcorn_quic_cc.API_VERSION)
Providers implement CongestionControllerFactory, validate their options, and
create one controller per QUIC network path. Controllers receive immutable
events and return validated SendLimits values.
Provider Discovery
Publish factories through the tigrcorn.quic_cc.v1 entry-point group. The
registry imports only the explicitly selected provider and rejects missing,
duplicate, or incompatible providers.
Compliance Helpers
DeterministicClock, collect_send_limits, and the public validators support
repeatable trace and invariant tests without importing Tigrcorn transports.
Related Packages
Package Graph
tigrcorn-core | tigrcorn-quic-cc | tigrcorn-quic-cc-reno | tigrcorn-config | tigrcorn-http | tigrcorn-asgi | tigrcorn-contract | tigrcorn-transports | tigrcorn-security | tigrcorn-protocols | tigrcorn-static | tigrcorn-observability | tigrcorn-runtime | tigrcorn-compat | tigrcorn-certification
tigrcorn-quic-cc is a layer-zero contract. Algorithm packages depend on it;
the transport depends on the contract and its default provider; runtime and
protocol packages consume the transport-owned enforcement surface.
Best Practices
- Keep controller state path-local.
- Treat event times as monotonic seconds and rates as bytes per second.
- Return finite, positive pacing rates and safe congestion windows.
- Keep packet loss detection, retransmission, and wire scheduling in Tigrcorn.
License
Apache-2.0
Metadata
Release files for tigrcorn-quic-cc 0.3.19
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tigrcorn_quic_cc-0.3.19.tar.gz | 15.5 kB | Without provenance | Details for tigrcorn_quic_cc-0.3.19.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrcorn_quic_cc-0.3.19-py3-none-any.whl | Python 3 | none | any | Details for tigrcorn_quic_cc-0.3.19-py3-none-any.whl |
Total release size: 30.9 kB
Release files / tigrcorn_quic_cc-0.3.19.tar.gz
| Download URL | tigrcorn_quic_cc-0.3.19.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
642a6c7da27228c6130b1c832c4d74cf82262a4082df5859a78ea5f124a5744f
|
|
BLAKE2b-256 checksum How to use checksums |
45310ff348c86c06d1f6af665b2f88e12fba664371553185e0d31f410c05542b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrcorn_quic_cc-0.3.19-py3-none-any.whl
| Download URL | tigrcorn_quic_cc-0.3.19-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dfa8571d06d50156a30176d96580a8c6a110abf4d823908135a2a04bbb5c346a
|
|
BLAKE2b-256 checksum How to use checksums |
10f0b0226a9c359cf9c83ef464f1b8085a28493b17d3c425ffb48abd074a1643
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrcorn-quic-cc 0.3.19
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.