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

question: Make imap-flow "sans I/O"? #154

Closed
duesee opened this issue Apr 1, 2024 · 3 comments · Fixed by #158
Closed

question: Make imap-flow "sans I/O"? #154

duesee opened this issue Apr 1, 2024 · 3 comments · Fixed by #158
Assignees

Comments

@duesee
Copy link
Owner

duesee commented Apr 1, 2024

See https://sans-io.readthedocs.io/ and https://fractalideas.com/blog/sans-io-when-rubber-meets-road/ I very much relate with what is written on the subject.

Examples

@duesee duesee modified the milestones: 9. Higher-level, async-first, IMAP library for client- and server, 9. Reworked: Higher-level, async-first, IMAP library for client- and server Apr 6, 2024
@jakoschiko
Copy link
Collaborator

This might solve problems like #98 or #134 (or at least move the responsibility to the user of imap-flow).

@jakoschiko
Copy link
Collaborator

On the other hand, this might remove our ability to force how the stream is handled, e.g. see duesee/imap-proxy#3.

@jakoschiko
Copy link
Collaborator

We might want to introduce an interface similar to rustls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants