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