a f’i.ã@s ddlmZGdd„deƒZdS)é)ÚTLObjectc@s$eZdZdZdZdd„Zdd„ZdS)Ú TLMessagea¥ https://core.telegram.org/mtproto/service_messages#simple-container. Messages are what's ultimately sent to Telegram: message msg_id:long seqno:int bytes:int body:bytes = Message; Each message has its own unique identifier, and the body is simply the serialized request that should be executed on the server, or the response object from Telegram. Since the body is always a valid object, it makes sense to store the object and not the bytes to ease working with them. There is no need to add serializing logic here since that can be inlined and is unlikely to change. Thus these are only needed to encapsulate responses. é cCs||_||_||_dS)N©Úmsg_idÚseq_noÚobj)Úselfrrr©r úO/home/ec2-user/.local/lib/python3.9/site-packages/telethon/tl/core/tlmessage.pyÚ__init__szTLMessage.__init__cCsd|j|j|jdœS)Nr)Ú_rrrr)r r r r Úto_dicts üzTLMessage.to_dictN)Ú__name__Ú __module__Ú __qualname__Ú__doc__Z SIZE_OVERHEADr rr r r r rsrN)Úrrr r r r Ús