1 Return-Path: <dme@dme.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 020A8431FAF
\r
6 for <notmuch@notmuchmail.org>; Sun, 15 Jan 2012 03:52:54 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[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 DIJbW07cdw77 for <notmuch@notmuchmail.org>;
\r
16 Sun, 15 Jan 2012 03:52:49 -0800 (PST)
\r
17 Received: from mail-we0-f181.google.com (mail-we0-f181.google.com
\r
18 [74.125.82.181]) (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 6FFCC431FAE
\r
21 for <notmuch@notmuchmail.org>; Sun, 15 Jan 2012 03:52:49 -0800 (PST)
\r
22 Received: by werh12 with SMTP id h12so657351wer.26
\r
23 for <notmuch@notmuchmail.org>; Sun, 15 Jan 2012 03:52:48 -0800 (PST)
\r
24 Received: by 10.216.136.38 with SMTP id v38mr1988744wei.23.1326628368283;
\r
25 Sun, 15 Jan 2012 03:52:48 -0800 (PST)
\r
26 Received: from hotblack-desiato.hh.sledj.net
\r
27 (host81-149-164-25.in-addr.btopenworld.com. [81.149.164.25])
\r
28 by mx.google.com with ESMTPS id fq7sm18194101wbb.1.2012.01.15.03.52.46
\r
29 (version=TLSv1/SSLv3 cipher=OTHER);
\r
30 Sun, 15 Jan 2012 03:52:46 -0800 (PST)
\r
31 Received: by hotblack-desiato.hh.sledj.net (Postfix, from userid 30000)
\r
32 id BEA1F9FEF2; Sun, 15 Jan 2012 11:52:44 +0000 (GMT)
\r
33 To: Pieter Praet <pieter@praet.org>, Austin Clements <amdragon@MIT.EDU>
\r
34 Subject: Re: [PATCH] Output unmodified Content-Type header value for JSON
\r
36 In-Reply-To: <87ehv2proa.fsf@praet.org>
\r
37 References: <1321659905-24367-1-git-send-email-dmitry.kurochkin@gmail.com>
\r
38 <87fwhkyisj.fsf@servo.finestructure.net> <87wrawq1dz.fsf@gmail.com>
\r
39 <87d3coxu7s.fsf@servo.finestructure.net> <87r512pru2.fsf@gmail.com>
\r
40 <87ipmewo4z.fsf@servo.finestructure.net>
\r
41 <20111123034021.GL9351@mit.edu> <87ipkglui4.fsf@praet.org>
\r
42 <20120112172840.GC18625@mit.edu> <87ehv2proa.fsf@praet.org>
\r
43 User-Agent: Notmuch/0.10.2+186~gd0f7804 (http://notmuchmail.org)
\r
44 Emacs/24.0.92.1 (x86_64-pc-linux-gnu)
\r
45 From: David Edmondson <dme@dme.org>
\r
46 Date: Sun, 15 Jan 2012 11:52:40 +0000
\r
47 Message-ID: <cun1ur16v3r.fsf@hotblack-desiato.hh.sledj.net>
\r
49 Content-Type: multipart/signed; boundary="=-=-=";
\r
50 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
51 Cc: notmuch@notmuchmail.org
\r
52 X-BeenThere: notmuch@notmuchmail.org
\r
53 X-Mailman-Version: 2.1.13
\r
55 List-Id: "Use and development of the notmuch mail system."
\r
56 <notmuch.notmuchmail.org>
\r
57 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
59 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
60 List-Post: <mailto:notmuch@notmuchmail.org>
\r
61 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
62 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
64 X-List-Received-Date: Sun, 15 Jan 2012 11:52:54 -0000
\r
67 Content-Type: text/plain
\r
69 > Technically the IRC discussion was about not including *any* part
\r
70 > content in the JSON output, and always using show --format=raw or
\r
71 > similar to retrieve desired parts. Currently, notmuch includes part
\r
72 > content in the JSON only for text/*, *except* when it's text/html. I
\r
73 > assume non-text parts are omitted because binary data is hard to
\r
74 > represent in JSON and text/html is omitted because some people don't
\r
75 > need it. However, this leads to some peculiar asymmetry in the Emacs
\r
76 > code where sometimes it pulls part content out of the JSON and
\r
77 > sometimes it retrieves it using show --format=raw. This in turn leads
\r
78 > to asymmetry in content encoding handling, since notmuch handles
\r
79 > content encoding for parts included in the JSON (and there's no good
\r
80 > way around that since JSON is Unicode), but not for parts retrieved as
\r
83 Including the text output in the JSON results in significantly fewer
\r
84 calls to 'notmuch' during the building of a typical `notmuch-show-mode'
\r
85 buffer. Someone with one of those older, crankier computers could easily
\r
86 test how much effect this has by changing
\r
87 `notmuch-show-get-bodypart-content' slightly.
\r
89 > The idea discussed on IRC was to remove all part content from the JSON
\r
90 > output and to always use show to retrieve it, possibly beefing up
\r
91 > show's support for content decoding (and possibly introducing a way to
\r
92 > retrieve multiple raw parts at once to avoid re-parsing). This would
\r
93 > get the JSON format out of the business of guessing what consumers
\r
94 > need, simplify the Emacs code, and normalize content encoding
\r
97 Is there a real problem being solved here? Having a clean structure is
\r
98 nice, except when it's not.
\r
101 Content-Type: application/pgp-signature
\r
103 -----BEGIN PGP SIGNATURE-----
\r
104 Version: GnuPG v1.4.11 (GNU/Linux)
\r
106 iEYEARECAAYFAk8SvgkACgkQaezQq/BJZRZLzwCfcogTyL3tMTxkO9Nr4bOdE6qO
\r
107 SSgAn0bQ/tyZLpmX/Dvi/6xlzZyC/gXt
\r
109 -----END PGP SIGNATURE-----
\r