imapserver: split command handling #554
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Split into two parts: parsing and processing. Some commands are incompatible with this model (e.g. APPEND), so will have a no-op second step. The goal is to parallelize the second step with other processing: reading the next command, and eventually handling the next command as well.
emersion
force-pushed
the
split-cmd-handling
branch
from
9a2351a to
ecd81dd
Compare
|
The main use-case for command pipelining is avoiding to stall the connection when executing long-running commands (e.g. a large SEARCH command). For FETCH the client can split up commands into bite-sized pieces. Maybe we should only implement this for SEARCH? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split into two parts: parsing and processing. Some commands are incompatible with this model (e.g. APPEND), so will have a no-op second step.
The goal is to parallelize the second step with other processing: reading the next command, and eventually handling the next command as well.