From: bdwalton@gmail.com (Ben Walton)
Subject: [sup-talk] IMAP server restart causes Sup exception
Date: Tue, 20 May 2008 12:23:31 -0400 [thread overview]
Message-ID: <f96e0240805200923r6eb46c9fwc53dcc99c63489d5@mail.gmail.com> (raw)
In-Reply-To: <1211299258-sup-2226@south>
On Tue, May 20, 2008 at 12:05 PM, William Morgan
<wmorgan-sup at masanjin.net> wrote:
> Interesting. I've had weird issues in the past with the Ruby IMAP
> library and threading, so this might be related. I've definitely seen it
> generate nonsensical backtraces by funny exception handling across
> threads.
I think you'll find that things get better if you do plain IMAP with
stunnel instead of relying on the ssl support in ruby/ruby-imap. I
had horrible (to the point where I almost had to switch away from
ruby) problems with a project that relied on the ability to do imaps.
The imap library may be partially to blame (and the imap spec
requiring threading doesn't help...), but I found that things got much
better without ssl being handled by ruby.
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <bdwalton at gmail.com>
When one person suffers from a delusion, it is called insanity. When
many people suffer from a delusion it is called Religion.
Robert M. Pirsig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2008-05-20 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 1:23 Kevin Riggle
2008-05-19 23:16 ` William Morgan
2008-05-20 15:03 ` Marcus Williams
2008-05-20 16:05 ` William Morgan
2008-05-20 16:23 ` Ben Walton [this message]
2008-05-25 2:45 ` William Morgan
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=f96e0240805200923r6eb46c9fwc53dcc99c63489d5@mail.gmail.com \
--to=bdwalton@gmail.com \
/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