Mongrel2 Transceiver was built to solve 3 major hassles that come with trying to handle ZMQ and WebSockets.
Handling WebSockets properly
Dynamically adding more connections to a running handlers
Reliably destroying ZMQ Contexts
Transceiver solves all these issues with an intuitive and simplistic syntax.
WARNING: Mongrel2 Transceiver was primarily designed to work with Docker containers. Therefore the default options for all the classes are not expecting to have issues binding to the default ports. It is your job to configure custom ports if you will be running in a single network environment. Every class has options for overriding the default ports and have been tested in a single network environment.
1 maintainer
Metadata
1 maintainer
Release files for mongrel2-transceiver 0.3.0
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 |
|---|---|---|---|---|
| mongrel2-transceiver-0.3.0.tar.gz | 22.8 kB | Without provenance | Details for mongrel2-transceiver-0.3.0.tar.gz |
Release files / mongrel2-transceiver-0.3.0.tar.gz
| Download URL | mongrel2-transceiver-0.3.0.tar.gz |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
baf603da10ec426a60d708a450858967149eedb4b90e8034d4b7e97313848397
|
|
BLAKE2b-256 checksum How to use checksums |
abf800cc2ef8a5bb46051b57f6d9abb1569568d9ae30dde4608bfdc1d2de5be7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mongrel2-transceiver 0.3.0
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.
