Replies: 3 comments 1 reply
-
Ok, to clarify this: UUIDs are big and inefficient, so, these are only used locally. Remote requests are tracked and distinguished by the |
Beta Was this translation helpful? Give feedback.
-
Oh, i think i did not express it clearly and caused misunderstanding.
And the uuid is randomly created by the tribler_core on each rest request, instead i would exptect core to receive it from the rest clients query strings, if not available create random by itself ie:
so that rest client will know the remote qurey result will match his own uuid. |
Beta Was this translation helpful? Give feedback.
-
Ok that would do, thanks for the answet |
Beta Was this translation helpful? Give feedback.
-
tribler/src/tribler-core/tribler_core/components/gigachannel/community/gigachannel_community.py
Line 204 in 87465a0
isnt random uuid supposed to be received from request query string so that in case multiple queires are made, the client can identify which response belongs to which?
@ichorid
Beta Was this translation helpful? Give feedback.
All reactions