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

type::Fetch flags ambiguity #98

Open
felinira opened this issue Dec 11, 2023 · 0 comments
Open

type::Fetch flags ambiguity #98

felinira opened this issue Dec 11, 2023 · 0 comments

Comments

@felinira
Copy link

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?

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