From mboxrd@z Thu Jan 1 00:00:00 1970 From: bwalton@artsci.utoronto.ca (Ben Walton) Date: Thu, 27 Aug 2009 19:39:20 -0400 Subject: [sup-talk] sent and draft sources In-Reply-To: <20090827200053.GA17416@chistera.yi.org> References: <1251402318-sup-4655@ntdws12.chass.utoronto.ca> <20090827200053.GA17416@chistera.yi.org> Message-ID: <1251416206-sup-4808@ntdws12.chass.utoronto.ca> 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: