How haivision/srt works
Project type and purpose
• This is an open-source protocol library (Secure Reliable Transport – SRT) implemented in C/C++.
• It provides:
• Core protocol engine (packetizing, ARQ, FEC, bonding, handshakes)
• Crypto abstraction layer (haicrypt) for AES encryption via OpenSSL, Botan, mbedTLS, or GnuTLS
• Sample CLI applications (srt-live-transmit, srt-file-transmit, etc.)
• Examples, tests, and build/deployment scripts for multiple platforms.
File structure
• Top-level:
• srtcore/ – core engine, API exposure, platform abstraction
• haicrypt/ – pluggable crypto backends
• apps/ – command-line tools demonstrating library usage
• examples/ – minimal code snippets showing client/server usage
• test/ & testing/ – unit tests and functional tests
• scripts/ – CMake helpers, platform build wrappers, installer scripts, CI workflows
• docs/, docs/API, docs/features, docs/build – architecture docs, API reference, feature descriptions, build guides
• Build: configure, CMakeLists.txt, per-platform CI YAMLs (.github/workflows, .travis.yml, appveyor).
• External dependencies are injected via CMake scripts (FindBotan, FindMbedTLS, OpenSSL, pthreads).
README for additional insights
• Confirms the protocol features (low-latency transport, ARQ/FEC, bonding, encryption).
• References to API documentation and sample applications.
• Build targets: Linux/macOS/iOS/Android/Windows, package managers.
Elements
• Labels for: Developer, Build System, srtcore (with submodules), haicrypt (interface + backends), Apps, Examples, Tests, External Dependencies, CI/CD
• Developer → Build System → Library+Apps
• Apps/Tests → srtcore → haicrypt → crypto backends
• srtcore → OS Socket API
• CI/CD → triggers Build System and runs Tests
• Orange for build artifacts/scripts