MBOX-Line: From tss at iki.fi  Sat Feb 16 12:54:58 2008
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] header.fields fetching
In-Reply-To: <PRxc2fMkEbRnGslXauDkeQ.md5@libertango.oryx.com>
References: <1203188859.4901.147.camel@hurina>
	<rLpAj0qCNeD2mVCkSSk87w.md5@libertango.oryx.com>
	<8782ACCD-1349-445D-BEAA-EB5409610D24@iki.fi>
	<oeGcRgEh/G5xGlxJ8jHQ3g.md5@libertango.oryx.com>
	<PRxc2fMkEbRnGslXauDkeQ.md5@libertango.oryx.com>
Message-ID: <54804692-077F-4D29-87DB-7F4BFA1B4A27@iki.fi>

On Feb 16, 2008, at 10:39 PM, Arnt Gulbrandsen wrote:

> All that said, treating a header field differently in HEADER.FIELDS  
> and HEADER.FIELDS.NOT sounds dubious to me. Not necessaribly wrong  
> by the RFCs, but I can't imagine why it would be desirable.

I noticed that one server already does this, and started wondering  
about doing something similar. This would allow caching headers by  
header ID -> value instead of header ID -> "header: value", i.e. saves  
a bit disk space. But since most mails use the same casing for header  
names, I guess this could be done in a fully standard way by  
allocating one bit to specify "header: is in its standardized  
presentation and it's not included in the value".

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 201 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080216/17422bbf/attachment.sig>
