cache capabilities and add capability?(name) #31

nevans · 2021-11-23T15:36:01Z

The client should keep track of server CAPABILITY responses and response codes. And it should invalidate previously cached values at the appropriate times (e.g. after STARTTLS).

The base spec requires this: (e.g. #32 LOGINDISABLED, #48 AUTH=). And many other extensions require the client to keep track (e.g. #37 LITERAL-). And the parser will also need to be able to "enable" different behavior for some extensions (e.g.
BINARY, UTF8=ACCEPT, IMAPrev2).

The text was updated successfully, but these errors were encountered:

This simplifies caching of the server capabilities, as many servers will send their capabilities inside the greeting. Needed for #31.

Added methods: * `#capable?(name)` - the main API for discovering capabilities * `#capabilities` - calls `capability` when needed * `#cached_capabilities` - accessor for cache; never contacts server * `#clear_cached_capabilities` - clears the cache; is thread safe Fixes ruby#31

Added methods: * `#capable?(name)` - the main API for discovering capabilities * `#capabilities` - calls `capability` when needed * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache; is thread safe Fixes ruby#31

Added methods: * `#capable?(name)` - the main API for discovering capabilities * `#auth_capable?(name)` - returns whether SASL mechanism is supported * `#capabilities` - calls `capability` when needed * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache; is thread safe Fixes ruby#31

Updated methods: * `#initialize` - save capabilities in `OK` or `PREAUTH` greeting * `#capability` - always update saved capabilities * `#starttls` - always clear capabilities after tagged OK response * `#authenticate` - clear capabilities or update from tagged OK response * `#login` - clear capabilities or update from tagged OK response New methods: * `#capable?(name)` - the primary API for discovering capabilities * `#auth_capable?(name)` - returns whether a SASL mechanism is supported * `#capabilities` - calls `capability` when needed * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache Fixes ruby#31

Updated methods: * `#initialize` - save capabilities in `OK` or `PREAUTH` greeting * `#capability` - always update saved capabilities * `#starttls` - always clear capabilities after tagged OK response * `#authenticate` - clear capabilities or update from tagged OK response * `#login` - clear capabilities or update from tagged OK response New methods: * `#capable?(name)` - the primary API for discovering capabilities * `#auth_capable?(name)` - returns whether a SASL mechanism is supported * `#capabilities` - calls `capability` when needed * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache Also, many docs related to capabilities wer reorganized and rewritten. Fixes ruby#31.

Updated methods: * `#initialize` - save capabilities in `OK` or `PREAUTH` greeting * `#capability` - always update saved capabilities * `#starttls` - always clear capabilities after tagged OK response * `#authenticate` - clear capabilities or update from tagged OK response * `#login` - clear capabilities or update from tagged OK response New methods: * `#capable?(name)` - the primary API for discovering capabilities * `#auth_capable?(name)` - returns whether a SASL mechanism is supported * `#capabilities` - calls `capability` when needed * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache Also, many docs related to capabilities were reorganized and rewritten. Fixes ruby#31.

Updated methods: * `#initialize` - save capabilities in `OK` or `PREAUTH` greeting * `#capability` - always update saved capabilities * `#starttls` - always clear capabilities after tagged OK response * `#authenticate` - clear capabilities or update from tagged OK response * `#login` - clear capabilities or update from tagged OK response New methods: * `#capable?(name)` - the primary API for discovering capabilities * `#auth_capable?(name)` - returns whether a SASL mechanism is supported * `#auth_mechanisms` - returns the server's supported SASL mechanisms * `#capabilities` - cached version of `capability` * `#capabilities_cached?` - whether capabilities are cached * `#clear_cached_capabilities` - clears the cache Also, the docs related to capabilities were reorganized and rewritten. Fixes ruby#31.

nevans mentioned this issue Nov 23, 2021

Support for IMAP4rev2 and modern extensions #12

Open

nevans changed the title ~~cache and add~~ cache capabilities and add capability?(name) Nov 23, 2021

This was referenced Nov 21, 2022

Net::IMAP Client docs #74

Merged

[🚧 WIP] SASL refactoring and new mechanisms #78

Closed

nevans added a commit that referenced this issue Jan 2, 2023

✨ Add greeting code data to responses

1b5e0cb

This simplifies caching of the server capabilities, as many servers will send their capabilities inside the greeting. Needed for #31.

nevans mentioned this issue Jan 2, 2023

✨ Add greeting code data to responses #94

Merged

nevans added a commit that referenced this issue Jan 6, 2023

✨ Add greeting code data to responses

10db63c

This simplifies caching of the server capabilities, as many servers will send their capabilities inside the greeting. Needed for #31.

nevans added a commit that referenced this issue Jan 7, 2023

✨ Add greeting code data to responses

4424213

This simplifies caching of the server capabilities, as many servers will send their capabilities inside the greeting. Needed for #31.

nevans added a commit that referenced this issue Jan 8, 2023

✨ Add greeting code data to responses

0304ca3

This simplifies caching of the server capabilities, as many servers will send their capabilities inside the greeting. Needed for #31.

nevans added the IMAP4rev1 Requirement for IMAP4rev1, RFC3501 label Feb 12, 2023

nevans mentioned this issue Jul 16, 2023

✨ Cache server capabilities and add #capable?(name) #156

Merged

nevans closed this as completed in #156 Jul 22, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cache capabilities and add capability?(name) #31

cache capabilities and add capability?(name) #31

nevans commented Nov 23, 2021 •

edited

Loading

cache capabilities and add capability?(name) #31

cache capabilities and add capability?(name) #31

Comments

nevans commented Nov 23, 2021 • edited Loading

nevans commented Nov 23, 2021 •

edited

Loading