You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The types::Fetch struct allows to iterate over flags no matter whether the field is actually returned by the server. It does not distinguish between the case of the fetch response not containing any flag updates and the message not having any flags. This is an issue for unsolicited fetch responses, as they might or might not contain any flag updates, leading to ambiguity.
Example: FETCH response with no flags set: 12 FETCH (FLAGS () UID 20)
Example: FETCH response with other data: 12 FETCH (UID 20)
There currently is no way to distinguish these two types of fetch responses via public API, right?
The text was updated successfully, but these errors were encountered:
The
types::Fetch
struct allows to iterate over flags no matter whether the field is actually returned by the server. It does not distinguish between the case of the fetch response not containing any flag updates and the message not having any flags. This is an issue for unsolicited fetch responses, as they might or might not contain any flag updates, leading to ambiguity.Example: FETCH response with no flags set:
12 FETCH (FLAGS () UID 20)
Example: FETCH response with other data:
12 FETCH (UID 20)
There currently is no way to distinguish these two types of fetch responses via public API, right?
The text was updated successfully, but these errors were encountered: