summaryrefslogtreecommitdiff
path: root/src/leap/bitmask
diff options
context:
space:
mode:
authorKali Kaneko <kali@leap.se>2015-03-05 12:26:51 -0400
committerRuben Pollan <meskio@sindominio.net>2015-03-10 19:00:46 +0100
commitfb68d7f9047e88e9c5bfb5dd1c74a62e7c3c77b4 (patch)
tree53fdcc1bd7ead77698fd836fe7d6ac3b5b42e060 /src/leap/bitmask
parente59e47675e92115f6c98b13cae518ede22e935eb (diff)
[doc] Remove unneded comment about collection refs
This concern is addressed by the following mail pullreq, that will be into 0.4.0 release: https://github.com/leapcode/leap_mail/pull/175 By the way, it is really funny that I cannot tell if this comment was written by meskio, as the blame says, or if I was the original author of the remark. I should stop drinking so much coffee.
Diffstat (limited to 'src/leap/bitmask')
-rw-r--r--src/leap/bitmask/services/mail/imap.py5
1 files changed, 0 insertions, 5 deletions
diff --git a/src/leap/bitmask/services/mail/imap.py b/src/leap/bitmask/services/mail/imap.py
index da753a0b..30646a63 100644
--- a/src/leap/bitmask/services/mail/imap.py
+++ b/src/leap/bitmask/services/mail/imap.py
@@ -93,11 +93,6 @@ def start_incoming_mail_service(keymanager, soledad, imap_factory, userid):
# the account, and passing the mailbox to the incoming service.
# In an even better world, we just would subscribe to a channel that would
# pass us the serialized object to be inserted.
- # XXX: I think we might be at risk here because the account top object
- # currently just returns as many mailbox objects as it's asked for, so
- # we should be careful about concurrent operations (ie, maybe just use
- # this one to do inserts, or let account have an in-memory map of
- # mailboxes, and just return references to them).
acc = imap_factory.theAccount
d = acc.callWhenReady(lambda _: acc.getMailbox(INBOX_NAME))
d.addCallback(setUpIncomingMail)