From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sent and draft sources
Date: Thu, 27 Aug 2009 19:39:20 -0400 [thread overview]
Message-ID: <1251416206-sup-4808@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <20090827200053.GA17416@chistera.yi.org>
Excerpts from Adeodato Sim?'s message of Thu Aug 27 16:00:53 -0400 2009:
> > I'd advise against having anything else write to the same mbox
> > (eg: don't have new mail delivered to the same source) if you go with
> > an mbox URI.
>
> Why? Would sup not lock the mbox properly?
No, it wouldn't. I've got a half-baked LockManager branch sitting
around, but I haven't touched it for some time now. I don't use any
mbox here myself so it's not a personal itch.
As it stands, the LockManager code has the basic ability to do
locking using three lock types. I haven't worked out the nicest way
to stack them (ala dovecot) though in a way that will play nicely with
threads _and_ allow for non-block-wrapped calling.
Thanks
-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/20090827/28664d43/attachment.bin>
next prev parent reply other threads:[~2009-08-27 23:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 19:44 Joe Shaw
2009-08-27 19:49 ` Ben Walton
2009-08-27 19:58 ` Joe Shaw
2009-08-28 20:31 ` William Morgan
2009-08-27 20:00 ` Adeodato Simó
2009-08-27 23:39 ` Ben Walton [this message]
2009-08-28 0:43 ` Ben Walton
2009-08-28 20:35 ` 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=1251416206-sup-4808@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