ClientManager::create_client_id identifies an instance; the request ID passed to send identifies an operation. Updates use request ID 0, so application requests must use nonzero IDs. Route by client first, then distinguish updates from responses.
A new instance emits no updates until its first request; simply creating it and waiting does not initialize it.
Send concurrently, receive consistently
Sending can occur from different threads, but receive must not run simultaneously on multiple threads. A timeout can return an empty object. Apply nonempty responses and updates in order. Synchronous execution is only for explicitly supported methods.
Resource-management recommendations
Give the receive loop and closure process clear ownership. Queue requests from UI actions. On closure, settle pending waiters and prevent stale callbacks from writing to destroyed screens. Log callbacks must not reenter TDLib.
The pinned header retains the older Client interface for compatibility. Choose one interface style consistently and consult the source for complete signatures and lifecycle comments.
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization
obtaining a copy of the software and accompanying documentation covered by
this license (the "Software") to use, reproduce, display, distribute,
execute, and transmit the Software, and to prepare derivative works of the
Software, and to permit third-parties to whom the Software is furnished to
do so, all subject to the following:
The copyright notices in the Software and this entire statement, including
the above license grant, this restriction and the following disclaimer,
must be included in all copies of the Software, in whole or in part, and
all derivative works of the Software, unless such copies or derivative
works are solely in the form of machine-executable object code generated by
a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT
SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE
FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
