5 Commits

Author	SHA1	Message	Date
Lonami Exo	3f16c92eb3	Subclass TLRequest for content-related objects	2018-06-12 20:14:21 +02:00
Lonami Exo	485ce5ca3b	Ignore padding on server messages instead warning ... There's 12..1024 padding for the MTProto 2.0 protocol, and the length of the message can be used to determine how much must be read on rpc_results. However this random padding can be safely ignored.	2018-06-09 14:23:42 +02:00
Lonami Exo	be279ce3f5	Make TLMessage always have a valid TLObject ... This simplifies the flow instead of having separate request/body attributes, and also means that BinaryReader.tgread_object() can be used without so many special cases.	2018-06-09 13:48:27 +02:00
Lonami Exo	f7e8907c6f	Create RpcResult class and generalise core special cases ... This results in a cleaner MTProtoSender, which now can always read a TLObject with a guaranteed item, if the message is OK.	2018-06-09 13:13:55 +02:00
Lonami Exo	adfe861e9f	Create a self-contained MTProtoState ... This frees us from using entire Session objects in something that's supposed to just send and receive items from the net.	2018-06-09 11:34:01 +02:00