diff options
author | sudden6 <sudden6@gmx.at> | 2019-11-14 13:11:13 +0100 |
---|---|---|
committer | sudden6 <sudden6@gmx.at> | 2020-01-02 11:58:52 +0100 |
commit | 683bc802e28934045d210ecb14609bde32de5d82 (patch) | |
tree | 86e3c24f4d91f0a760b5a89803b35689a6e68d65 /toxav/toxav.h | |
parent | 1b7d7b66c5221133abc5137e2cb3fa349491ae72 (diff) |
fix ToxAV threading documentation
ToxAV is not thread-safe at the moment, remove that claim from the
header file.
Diffstat (limited to 'toxav/toxav.h')
-rw-r--r-- | toxav/toxav.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/toxav/toxav.h b/toxav/toxav.h index bfb7617c..daa1314d 100644 --- a/toxav/toxav.h +++ b/toxav/toxav.h | |||
@@ -49,8 +49,8 @@ extern "C" { | |||
49 | */ | 49 | */ |
50 | /** \subsection threading Threading implications | 50 | /** \subsection threading Threading implications |
51 | * | 51 | * |
52 | * Unlike the Core API, this API is fully thread-safe. The library will ensure | 52 | * Only toxav_iterate is thread-safe, all other functions must run from the |
53 | * the proper synchronization of parallel calls. | 53 | * tox thread. |
54 | * | 54 | * |
55 | * A common way to run ToxAV (multiple or single instance) is to have a thread, | 55 | * A common way to run ToxAV (multiple or single instance) is to have a thread, |
56 | * separate from tox instance thread, running a simple toxav_iterate loop, | 56 | * separate from tox instance thread, running a simple toxav_iterate loop, |