qiurui
/
uvgrtp-base
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Update links in docs folder to examples folder

This commit is contained in:
Joni Räsänen 2022-02-28 12:08:25 +02:00
parent 154f50ee94
commit f15908909e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/README.md
View File

@ -31,7 +31,7 @@ Currently uvgRTP has a built-in support for the following media formats:
* Opus * Opus
uvgRTP also features a generic media frame API that can be used to fragment and send any media format, uvgRTP also features a generic media frame API that can be used to fragment and send any media format,
see [this example code](examples/sending_generic.cc) for more details. Fragmentation of generic media formats is a uvgRTP exclusive feature and does not work with other RTP libraries so please use it only if you are using uvgRTP for both sending and receiving. see [this example code](../examples/sending_generic.cc) for more details. Fragmentation of generic media formats is a uvgRTP exclusive feature and does not work with other RTP libraries so please use it only if you are using uvgRTP for both sending and receiving.
## Context configuration ## Context configuration
@ -83,7 +83,7 @@ whereas for user-managed keys the calling application must provide an encryption
uvgRTP supports Diffie-Hellman and Multistream modes of ZRTP. The mode selection is done transparently uvgRTP supports Diffie-Hellman and Multistream modes of ZRTP. The mode selection is done transparently
and the only thing an application must do is to provide `RCE_SRTP | RCE_SRTP_KMNGMNT_ZRTP` flag combination and the only thing an application must do is to provide `RCE_SRTP | RCE_SRTP_KMNGMNT_ZRTP` flag combination
to `create_stream()`. See [ZRTP Multistream example](examples/zrtp_multistream.cc) for more details. to `create_stream()`. See [ZRTP Multistream example](../examples/zrtp_multistream.cc) for more details.
### User-managed SRTP ### User-managed SRTP
@ -91,4 +91,4 @@ The second way of handling key-management of SRTP is to do it yourself. uvgRTP s
and and 112-bit salts which must be given to the `uvgrtp::media_stream` object using `add_srtp_ctx()` right after and and 112-bit salts which must be given to the `uvgrtp::media_stream` object using `add_srtp_ctx()` right after
`create_stream()` has been called. All calls that try to modify or use the stream `create_stream()` has been called. All calls that try to modify or use the stream
(other than `add_srtp_ctx()`) will fail with `RTP_NOT_INITIALIZED`. (other than `add_srtp_ctx()`) will fail with `RTP_NOT_INITIALIZED`.
See [this example code](examples/srtp_user.cc) for more details. See [this example code](../examples/srtp_user.cc) for more details.