Re: About the json output and the number of results shown.

diff --git a/7b/eb0d01729861c67e7c93c7ef04ea455357b111 b/7b/eb0d01729861c67e7c93c7ef04ea455357b111
new file mode 100644 (file)
index 0000000..74bdf83
--- /dev/null
+++ b/7b/eb0d01729861c67e7c93c7ef04ea455357b111
@@ -0,0 +1,101 @@
+Return-Path: <jdub@bethesignal.org>\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 A8E7D431FB6\r
+       for <notmuch@notmuchmail.org>; Sat, 12 Feb 2011 22:29:56 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+       tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\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 zX05MGyYOqyL for <notmuch@notmuchmail.org>;\r
+       Sat, 12 Feb 2011 22:29:55 -0800 (PST)\r
+Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com\r
+       [209.85.212.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 9858C431FB5\r
+       for <notmuch@notmuchmail.org>; Sat, 12 Feb 2011 22:29:55 -0800 (PST)\r
+Received: by vws8 with SMTP id 8so2612101vws.26\r
+       for <notmuch@notmuchmail.org>; Sat, 12 Feb 2011 22:29:52 -0800 (PST)\r
+MIME-Version: 1.0\r
+Received: by 10.220.75.20 with SMTP id w20mr3108401vcj.34.1297578592171; Sat,\r
+       12 Feb 2011 22:29:52 -0800 (PST)\r
+Received: by 10.220.86.135 with HTTP; Sat, 12 Feb 2011 22:29:52 -0800 (PST)\r
+X-Originating-IP: [150.101.115.228]\r
+In-Reply-To: <87pqrgn4nr.fsf@yoom.home.cworth.org>\r
+References: <AANLkTi=Mzu9bu3y0RKB5YZUpZOT9qujXgxtpB-8Bvk=2@mail.gmail.com>\r
+       <87pqrgn4nr.fsf@yoom.home.cworth.org>\r
+Date: Sun, 13 Feb 2011 17:29:52 +1100\r
+Message-ID: <AANLkTi=6c6J2f4JkF0LLa=sN1VEKbZOXBBn4hd4jY2Nv@mail.gmail.com>\r
+Subject: Re: About the json output and the number of results shown.\r
+From: Jeff Waugh <jdub@bethesignal.org>\r
+To: notmuch@notmuchmail.org\r
+Content-Type: multipart/alternative; boundary=0016e65c8a4a0df6fe049c240f25\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: Sun, 13 Feb 2011 06:29:56 -0000\r
+\r
+--0016e65c8a4a0df6fe049c240f25\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+On Sat, Jan 29, 2011 at 07:40, Carl Worth wrote:\r
+\r
+> One idea I've had for this is to change the output (perhaps with a\r
+> command-line option) to avoid emitting the outer array. That is, the\r
+> results would instead be a series of independent JSON objects rather\r
+> than a single JSON object. That should let the application treat things\r
+> quickly by simply calling the JSON parser for each complete\r
+> object.\r
+\r
+\r
+It might be useful to model this on the Twitter streaming API, which just\r
+delivers a lot of JSON + '\r\n' (large objects straddle http chunks).\r
+\r
+\r
+> (Though, here, the application would likely want a cheap way to\r
+> know when the input represented a complete object.)\r
+>\r
+\r
+Is that necessary? You're definitely going to get a \r\n or an EOF at some\r
+point. :-)\r
+\r
+- Jeff\r
+\r
+--0016e65c8a4a0df6fe049c240f25\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<div class=3D"gmail_quote">On Sat, Jan 29, 2011 at 07:40, Carl Worth=C2=A0w=\r
+rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=\r
+r-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">One idea I&#39;v=\r
+e had for this is to change the output (perhaps with a</div>\r
+\r
+command-line option) to avoid emitting the outer array. That is, the<br>\r
+results would instead be a series of independent JSON objects rather<br>\r
+than a single JSON object. That should let the application treat things<br>\r
+quickly by simply calling the JSON parser for each complete<br>\r
+object.</blockquote><div><br></div><div>It might be useful to model this on=\r
+ the Twitter streaming API, which just delivers a lot of JSON + &#39;\r\n&#=\r
+39; (large objects straddle http chunks).</div><div>=C2=A0</div><blockquote=\r
+ class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=\r
+d;padding-left:1ex;">\r
+ (Though, here, the application would likely want a cheap way to<br>\r
+know when the input represented a complete object.)<br></blockquote><div><b=\r
+r></div><div>Is that necessary? You&#39;re definitely going to get a \r\n o=\r
+r an EOF at some point. :-)</div><div><br></div><div>- Jeff</div></div>\r
+\r
+--0016e65c8a4a0df6fe049c240f25--\r