Refactor IMAP code into a distinct crate #140

Closed
opened 2021-08-03 07:39:26 +03:00 by ryzokuken · 1 comment

This one's probably way more complicated, but let's refactor the IMAP client code into sub-crates, possibly even moving it to another repo so that they could be reused elsewhere conveninently.

Current options for IMAP client libs:

/cc @epilys

This one's probably way more complicated, but let's refactor the IMAP client code into sub-crates, possibly even moving it to another repo so that they could be reused elsewhere conveninently. Current options for IMAP client libs: * https://github.com/jonhoo/rust-imap (seems sync) * https://github.com/djc/tokio-imap (async, uses `tokio`) * https://github.com/async-email/async-imap (async, uses `async_std`) /cc @epilys

Closing this, unless someone wants to pick it up.

Closing this, unless someone wants to pick it up.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: meli/meli#140
There is no content yet.