From cdafc6ff5ee13595ecf5a4e1fe0cb28e255c37df Mon Sep 17 00:00:00 2001 From: zoff99 Date: Thu, 9 Apr 2020 20:07:32 +0200 Subject: Add new semi-private API functions to set per-packet-id custom handlers. This is to prepare for ToxAV becoming independent of toxcore internal calls. --- toxcore/tox.api.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'toxcore/tox.api.h') diff --git a/toxcore/tox.api.h b/toxcore/tox.api.h index 5e42b866..3cda8126 100644 --- a/toxcore/tox.api.h +++ b/toxcore/tox.api.h @@ -2670,7 +2670,7 @@ namespace friend { FRIEND_NOT_CONNECTED, /** * The first byte of data was not in the specified range for the packet type. - * This range is 200-254 for lossy, and 160-191 for lossless packets. + * This range is 192-254 for lossy, and 69, 160-191 for lossless packets. */ INVALID, /** @@ -2692,7 +2692,7 @@ namespace friend { /** * Send a custom lossy packet to a friend. * - * The first byte of data must be in the range 200-254. Maximum length of a + * The first byte of data must be in the range 192-254. Maximum length of a * custom packet is $MAX_CUSTOM_PACKET_SIZE. * * Lossy packets behave like UDP packets, meaning they might never reach the @@ -2716,7 +2716,7 @@ namespace friend { /** * Send a custom lossless packet to a friend. * - * The first byte of data must be in the range 160-191. Maximum length of a + * The first byte of data must be in the range 69, 160-191. Maximum length of a * custom packet is $MAX_CUSTOM_PACKET_SIZE. * * Lossless packet behaviour is comparable to TCP (reliability, arrive in order) -- cgit v1.2.3