mirror of
https://github.com/LonamiWebs/Telethon.git
synced 2024-12-02 14:23:45 +03:00
54 lines
1.8 KiB
Python
54 lines
1.8 KiB
Python
import asyncio
|
|
import struct
|
|
|
|
from .gzippacked import GzipPacked
|
|
from .. import TLObject
|
|
from ..functions import InvokeAfterMsgRequest
|
|
|
|
|
|
class TLMessage(TLObject):
|
|
"""
|
|
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. Then
|
|
Telegram will, at some point, respond with the result for this msg.
|
|
|
|
Thus it makes sense that requests and their result are bound to a
|
|
sent `TLMessage`, and this result can be represented as a `Future`
|
|
that will eventually be set with either a result, error or cancelled.
|
|
"""
|
|
def __init__(self, msg_id, seq_no, obj=None, after_id=0):
|
|
self.msg_id = msg_id
|
|
self.seq_no = seq_no
|
|
self.obj = obj
|
|
self.container_msg_id = None
|
|
self.future = asyncio.Future()
|
|
|
|
# After which message ID this one should run. We do this so
|
|
# InvokeAfterMsgRequest is transparent to the user and we can
|
|
# easily invoke after while confirming the original request.
|
|
self.after_id = after_id
|
|
|
|
def to_dict(self):
|
|
return {
|
|
'_': 'TLMessage',
|
|
'msg_id': self.msg_id,
|
|
'seq_no': self.seq_no,
|
|
'obj': self.obj,
|
|
'container_msg_id': self.container_msg_id,
|
|
'after_id': self.after_id
|
|
}
|
|
|
|
def __bytes__(self):
|
|
if self.after_id is None:
|
|
body = GzipPacked.gzip_if_smaller(self.obj)
|
|
else:
|
|
body = GzipPacked.gzip_if_smaller(
|
|
InvokeAfterMsgRequest(self.after_id, self.obj))
|
|
|
|
return struct.pack('<qii', self.msg_id, self.seq_no, len(body)) + body
|