https://github.com/awslabs/amazon-kinesis-video-streams-signaling
https://github.com/awslabs/amazon-kinesis-video-streams-signaling
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.3%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: awslabs
- License: apache-2.0
- Language: C
- Default Branch: main
- Size: 184 KB
Statistics
- Stars: 2
- Watchers: 10
- Forks: 2
- Open Issues: 0
- Releases: 0
Metadata Files
README.md
amazon-kinesis-video-streams-signaling
The goal of the Signaling library is to enable communication with the Amazon Kinesis Video Signaling Service. Refer to AWS KVS API Reference and WebRTC Websocket APIs for more details.
What is Signaling?
The Amazon Kinesis Video Signaling Service facilitates peer-to-peer communication by providing signaling channels that enable applications to discover, establish, control, and terminate connections through the exchange of signaling messages. This library provides APIs to construct requests to send to the Signaling Service and to parse responses from the Signaling Service.
- Note that this library has a dependency on coreJSON.
Using the library
- Use the
Signaling_Construct*APIs to construct requests to send to the Signaling Service.- Ensure to authenticate and sign the constructed requests using the Signature Version 4 (SigV4) authentication flow before sending them.
- Use the
Signaling_Parse*APIs to parse the responses from the Signaling Service. - Use
Signaling_ConstructWssMessageandSignaling_ParseWssRecvMessageAPIs to communicate with the WSS endpoint.- Ensure to authenticate and sign the constructed messages using the Signature Version 4 (SigV4) authentication flow before sending them.
Building Unit Tests
Platform Prerequisites
- For running unit tests:
- C99 compiler like gcc.
- CMake 3.13.0 or later.
- Ruby 2.0.0 or later (It is required for the CMock test framework that we use).
- For running the coverage target, gcov and lcov are required.
Steps to Build Unit Tests
- The following command in STEP 2 also ensures that the Submodules ( CMock and coreJSON ) are added.
Run the following command to generate Makefiles:
sh cmake -S test/unit-test -B build/ -G "Unix Makefiles" \ -DCMAKE_BUILD_TYPE=Debug \ -DBUILD_CLONE_SUBMODULES=ON \ -DCMAKE_C_FLAGS='--coverage -Wall -Wextra -Werror -DNDEBUG'
Steps to Generate Code Coverage Report and Run Unit Tests
- Run Unit Tests in Steps to Build Unit Tests.
Generate coverage report in the
build/coveragefolder:cd build && make coverage
Script to Run Unit Test and Generate Code Coverage Report
sh
cmake -S test/unit-test -B build/ -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug -DBUILD_CLONE_SUBMODULES=ON -DCMAKE_C_FLAGS='--coverage -Wall -Wextra -Werror -DNDEBUG -DLIBRARY_LOG_LEVEL=LOG_DEBUG'
cd build && make coverage
License
This project is licensed under the Apache-2.0 License.
Owner
- Name: Amazon Web Services - Labs
- Login: awslabs
- Kind: organization
- Location: Seattle, WA
- Website: http://amazon.com/aws/
- Repositories: 914
- Profile: https://github.com/awslabs
AWS Labs
GitHub Events
Total
- Delete event: 2
- Issue comment event: 1
- Push event: 5
- Pull request review event: 36
- Pull request review comment event: 19
- Pull request event: 9
- Fork event: 2
- Create event: 2
Last Year
- Delete event: 2
- Issue comment event: 1
- Push event: 5
- Pull request review event: 36
- Pull request review comment event: 19
- Pull request event: 9
- Fork event: 2
- Create event: 2
Issues and Pull Requests
Last synced: about 2 years ago
All Time
- Total issues: 0
- Total pull requests: 2
- Average time to close issues: N/A
- Average time to close pull requests: 2 days
- Total issue authors: 0
- Total pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 2
- Average time to close issues: N/A
- Average time to close pull requests: 2 days
- Issue authors: 0
- Pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- Varunaditya1 (1)
Pull Request Authors
- ActoryOu (5)
- Varunaditya1 (3)
- t2-g (1)
- moninom1 (1)