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

Don't check for capabilities in protocol #49

Open
filiphanes opened this issue Jul 24, 2020 · 0 comments
Open

Don't check for capabilities in protocol #49

filiphanes opened this issue Jul 24, 2020 · 0 comments

Comments

@filiphanes
Copy link

Hi,
I think that user should be responsible to check for capabilities supported by IMAP server and use only them.
Library should not restrict user this way.

  1. If capability is not supported, server returns BAD or NO response.
  2. With checking in protocol, user could not use this lib with server which supports capability, but doesn't advertise it, for example because it is only partially implemented.
  3. It is additional check in every request, protocol should be fast. Of course it isn't significant, but it's a point.
  4. It is even more work for correctly checking for advanced capabilities like CONDSTORE, QRESYNC, LIST-STATUS.
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