1 Return-Path: <cworth@cworth.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id A94F9429E25
\r
6 for <notmuch@notmuchmail.org>; Thu, 27 Jan 2011 21:15:36 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5
\r
12 tests=[ALL_TRUSTED=-1, T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id AF1ZiJb2Ihne; Thu, 27 Jan 2011 21:15:35 -0800 (PST)
\r
16 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
17 by olra.theworths.org (Postfix) with ESMTP id 42210429E22;
\r
18 Thu, 27 Jan 2011 21:15:35 -0800 (PST)
\r
19 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
20 id D652654C005; Fri, 28 Jan 2011 15:10:01 +1000 (EST)
\r
21 From: Carl Worth <cworth@cworth.org>
\r
22 To: Austin Clements <amdragon@mit.edu>,
\r
23 Jameson Rollins <jrollins@finestructure.net>
\r
24 Subject: Re: notmuch's idea of concurrency / failing an invocation
\r
25 In-Reply-To: <AANLkTi=pPgcPXUN_XTXa0gAkbTR_OF4XxCP-d4-Be2pt@mail.gmail.com>
\r
26 References: <87fwsetdin.fsf@kepler.schwinge.homeip.net>
\r
27 <8762taxk9y.fsf@algae.riseup.net>
\r
28 <87vd1a84qj.fsf@servo.finestructure.net>
\r
29 <AANLkTi=pPgcPXUN_XTXa0gAkbTR_OF4XxCP-d4-Be2pt@mail.gmail.com>
\r
30 User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1
\r
32 Date: Fri, 28 Jan 2011 15:10:01 +1000
\r
33 Message-ID: <87fwsdobpy.fsf@yoom.home.cworth.org>
\r
35 Content-Type: multipart/signed; boundary="=-=-=";
\r
36 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
37 Cc: notmuch@notmuchmail.org, Thomas Schwinge <thomas@schwinge.name>
\r
38 X-BeenThere: notmuch@notmuchmail.org
\r
39 X-Mailman-Version: 2.1.13
\r
41 List-Id: "Use and development of the notmuch mail system."
\r
42 <notmuch.notmuchmail.org>
\r
43 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
44 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
45 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
46 List-Post: <mailto:notmuch@notmuchmail.org>
\r
47 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
48 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
50 X-List-Received-Date: Fri, 28 Jan 2011 05:15:37 -0000
\r
53 Content-Transfer-Encoding: quoted-printable
\r
55 On Thu, 27 Jan 2011 17:20:21 -0500, Austin Clements <amdragon@mit.edu> wrot=
\r
57 > I'm looking into breaking notmuch new up into small transactions. It
\r
58 > wouldn't be much a leap from there to simply close and reopen the database
\r
59 > between transactions if another task wants to use it, which would release
\r
60 > the lock and let the queued notmuch task have the database for a bit.
\r
62 That sounds like something very useful to pursue. Please continue!
\r
64 > It seems silly to have a daemon when all of notmuch's state is already on=
\r
66 > and queue on a lock is as good as a queue in a daemon, but without the
\r
67 > accompanying architectural shenanigans.
\r
69 It would definitely be nice to avoid the complexity inherent in having a
\r
70 daemon, but how do you imagine "queue on a lock" to work? We don't have
\r
71 anything like that in place now.
\r
73 Another advantage that can happen with queueing (wherever it occurs) is
\r
74 to allow a client to be very responsive without waiting for an operation
\r
75 to complete. Though that can of course be band if the operation isn't
\r
81 carl.d.worth@intel.com
\r
84 Content-Type: application/pgp-signature
\r
86 -----BEGIN PGP SIGNATURE-----
\r
87 Version: GnuPG v1.4.10 (GNU/Linux)
\r
89 iD8DBQFNQk+p6JDdNq8qSWgRAhCAAJ9JPy5w1JOWlCAyc34lIhRlpCEn7gCeO3bg
\r
90 yBbq+40sV+jlv0HkCnjkjEY=
\r
92 -----END PGP SIGNATURE-----
\r