Re: Second draft of logging patches

diff --git a/2e/622f7f7e29f52ea1580a8944ed7093a500b6b8 b/2e/622f7f7e29f52ea1580a8944ed7093a500b6b8
new file mode 100644 (file)
index 0000000..411bb22
--- /dev/null
+++ b/2e/622f7f7e29f52ea1580a8944ed7093a500b6b8
@@ -0,0 +1,74 @@
+Return-Path: <bremner@unb.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 7E6EB40DBD7\r
+       for <notmuch@notmuchmail.org>; Tue,  9 Nov 2010 19:18:39 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.6\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5\r
+       tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id qA6xIT2hOasJ for <notmuch@notmuchmail.org>;\r
+       Tue,  9 Nov 2010 19:18:28 -0800 (PST)\r
+Received: from tempo.its.unb.ca (tempo.its.unb.ca [131.202.1.21])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id A147640DBC9\r
+       for <notmuch@notmuchmail.org>; Tue,  9 Nov 2010 19:18:28 -0800 (PST)\r
+Received: from rocinante.cs.unb.ca\r
+       (fctnnbsc30w-142167176217.pppoe-dynamic.High-Speed.nb.bellaliant.net\r
+       [142.167.176.217]) (authenticated bits=0)\r
+       by tempo.its.unb.ca (8.13.8/8.13.8) with ESMTP id oAA3INs4016728\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO);\r
+       Tue, 9 Nov 2010 23:18:26 -0400\r
+Received: from bremner by rocinante.cs.unb.ca with local (Exim 4.72)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1PG1CX-000536-4T; Tue, 09 Nov 2010 23:18:21 -0400\r
+From: David Bremner <david@tethera.net>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: Second draft of logging patches\r
+In-Reply-To: <1287954066-24512-1-git-send-email-david@tethera.net>\r
+References: <1286803617-17328-1-git-send-email-david@tethera.net>\r
+       <1287954066-24512-1-git-send-email-david@tethera.net>\r
+User-Agent: Notmuch/0.3.1-59-g676d251 (http://notmuchmail.org) Emacs/23.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Tue, 09 Nov 2010 23:18:19 -0400\r
+Message-ID: <877hgln9xg.fsf@rocinante.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 10 Nov 2010 03:18:39 -0000\r
+\r
+On Sun, 24 Oct 2010 18:01:02 -0300, david@tethera.net wrote:\r
+> Here is my second try at logging, taking into account the feedback I\r
+> got from Rob and Michal.  There is definitely some tidying to do; in\r
+> particular I know the protoypes in public headers need\r
+> documentation. Also, I should add a configuration option to\r
+> enable configuration by command or something like that.\r
+\r
+I had a thought of a possibly interesting application of the (yet to be\r
+written) log playback code. It could be use to implement a simple\r
+queuing system where commands are only logged but not actually run on\r
+the database. I'm not sure about the performance implications, but it\r
+could be interesting because it eliminates the need to have a server\r
+running in order to eliminate write contention for the tag database.\r
+The "queue runner" could be as simple as a cron job, or it could be\r
+something spawned by one of the queue operations; the point would be\r
+that queueing could continue while the snapshot of the queue was run.\r
+\r
+d\r