diff options
author | Simon Ser <contact@emersion.fr> | 2019-04-28 13:01:56 +0000 |
---|---|---|
committer | Drew DeVault <sir@cmpwn.com> | 2019-04-29 09:49:22 -0400 |
commit | 089740758c0f408a62de331990fe694d35bc8d1c (patch) | |
tree | 9249c0fdf8752fb782862251fd6f62dabb8c871d /widgets/msglist.go | |
parent | 072bc268723957f235edcff7b45fd41b04ccab27 (diff) | |
download | aerc-089740758c0f408a62de331990fe694d35bc8d1c.tar.gz |
worker/imap: use the IMAP connection from a single goroutine
Unfortunately, the IMAP protocol hasn't been designed to be used from multiple goroutines at the same time. For instance, if you fetch twice the same message from two different goroutines, it's not possible to tell whether the response is for one receiver or the other. For this reason, go-imap clients aren't safe to use from multiple goroutines. This commit changes the IMAP workers to be synchronous again (a command is executed only after the previous one has completed). To use IMAP from different threads, popular clients (e.g. Thunderbird) typically open multiple connections.
Diffstat (limited to 'widgets/msglist.go')
0 files changed, 0 insertions, 0 deletions