diff --git a/data/web/corefork.telegram.org/api/files.html b/data/web/corefork.telegram.org/api/files.html index f33dec8230..5e6a1bfe88 100644 --- a/data/web/corefork.telegram.org/api/files.html +++ b/data/web/corefork.telegram.org/api/files.html @@ -109,7 +109,7 @@ After the entire file is successfully saved, the final method may be called and

Albums, grouped media

inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
@@ -507,7 +507,10 @@ In normal chats document should always be provided instead of 
 
 

General Considerations

-

It is recommended that large queries (upload.getFile, upload.saveFilePart, upload.getWebFile) be handled through a separate session and a separate connection, in which no methods other than these should be executed. If this is done, then data transfer will cause less interference with getting updates and other method calls.

+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true this_port_only:flags.5?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+

It is recommended that large queries (upload.getFile, upload.saveFilePart, upload.getWebFile) be handled through one or more separate sessions and separate connections, in which no methods other than these should be executed.
+This way, data transfer will cause less interference with getting updates and other method calls.
+If a media DC with the required DC ID is available (dcOption will have the media flag set), queries must be sent to that DC.

Related articles

Handling file references

How to handle file references.