From 2ac0e20a6af2786ae7b66d0b15e74346047e76ac Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 5 Feb 2022 19:33:29 +0000 Subject: [PATCH] Update content of files --- data/core.telegram.org/tdlib/getting-started.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/core.telegram.org/tdlib/getting-started.html b/data/core.telegram.org/tdlib/getting-started.html index e61886059b..d5ee3a802d 100644 --- a/data/core.telegram.org/tdlib/getting-started.html +++ b/data/core.telegram.org/tdlib/getting-started.html @@ -41,7 +41,7 @@
-

TDLib is a fully functional Telegram client which takes care of all networking, local storage and data consistency details. In this tutorial we describe the main concepts understanding of which is required for effecient TDLib usage.

+

TDLib is a fully functional Telegram client which takes care of all networking, local storage and data consistency details. In this tutorial we describe the main concepts understanding of which is required for efficient TDLib usage.

TDLib interface

In this text, Client means an interface for interaction with a TDLib instance and Application means the program that uses TDLib to interact with Telegram.

The main TDLib API is fully-asyncronous. An Application can send a request to TDLib through ClientManager.send method and receive a response asynchronously through the ClientManager.receive method when it becomes available. The exact naming of these methods and the way in which requests are matched with responses is different for different TDLib interfaces, but the concept as a whole remains the same. For example, in TDLib JSON interface these methods are called td_send and td_receive, and their @extra field must be used to match requests with the corresponding responses.