Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extended Voluntary Communication of Status of One Message #46

Open
aykutalparslan opened this issue Mar 1, 2022 · 0 comments
Open

Extended Voluntary Communication of Status of One Message #46

aykutalparslan opened this issue Mar 1, 2022 · 0 comments

Comments

@aykutalparslan
Copy link
Owner

Normally used by the server to respond to the receipt of a duplicate msg_id, especially if a response to the message has already been generated and the response is large. If the response is small, the server may re-send the answer itself instead. This message can also be used as a notification instead of resending a large message.

msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;

The second version is used to notify of messages that were created on the server not in response to an RPC query (such as notifications of new messages) and were transmitted to the client some time ago, but not acknowledged.

Currently, status is always zero. This may change in future.

This message does not require an acknowledgment.

@aykutalparslan aykutalparslan added this to the 6. Service Messages and Low Level API milestone Mar 1, 2022
@aykutalparslan aykutalparslan removed this from the 06. Service Messages and Low Level API milestone Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant