From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sup opens multiple connections to the same imap-server
Date: Sat, 11 Jul 2009 10:12:17 -0400 [thread overview]
Message-ID: <1247321064-sup-4795@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1247185833-sup-8539@x200>
Excerpts from Michael Stapelberg's message of Thu Jul 09 20:34:21 -0400 2009:
> Is there an easy way to make sup use only one connection? If not, I?ll see
> if this problem still arises after I re-install my server (probably with
> dovecot instead of cyrus this time).
I don't believe there is a way to do this currently. It would require
some refactoring of the code.
Roughly:
The IMAP source would refer to an IMAPManager for a connection. The
IMAP manager would handle creating new connections when required or
passing a reference to an existing connection if it had already
created. A tuple of (imap server, username, password) could be used
to determine the uniqueness of the request.
The unsafe_connect method of the IMAP source could move to the
IMAPManager and calls to unsafe_connect could be rerouted to
IMAPManager.connection_for(server, user, password) or some such...
It shouldn't be a bad addition to add if you're interested.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090711/4edae96c/attachment.bin>
next prev parent reply other threads:[~2009-07-11 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 0:34 Michael Stapelberg
2009-07-11 14:12 ` Ben Walton [this message]
2009-07-11 15:36 ` Michael Stapelberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1247321064-sup-4795@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox