From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.87.14 with SMTP id k14cs1235645agb; Wed, 30 Dec 2009 06:11:02 -0800 (PST) Received: by 10.229.23.74 with SMTP id q10mr2131936qcb.63.1262182262511; Wed, 30 Dec 2009 06:11:02 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 3si20307661qyk.34.2009.12.30.06.11.02; Wed, 30 Dec 2009 06:11:02 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 08D4B19782DC; Wed, 30 Dec 2009 09:11:02 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 323E818581EF for ; Wed, 30 Dec 2009 09:10:55 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1NPzGJ-0006Df-LI for sup-devel@rubyforge.org; Wed, 30 Dec 2009 06:10:55 -0800 From: William Morgan To: sup-devel In-reply-to: <1262136474-sup-312@tilus.net> References: <1261485246-sup-4236@tilus.net> <1261938751-sup-9421@zyrg.net> <1262136474-sup-312@tilus.net> Date: Wed, 30 Dec 2009 06:10:54 -0800 Message-Id: <1262182085-sup-1405@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] [PATCH] XapianIndex.each_message_in_thread_for yields messages in cronological order X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Reformatted excerpts from Tero Tilus's message of 2009-12-29: > For what I know you might trigger this by replying to many messages at > once and thus having a list of ids in-reply-to header (in whatever > order of course, rfc doesn't require any particular order) instead of > one. Then when you reply to this message using MUA that is bold > enough to try to form References: with the standard in-reply-to + > my-id method even if RFC 2822 says "trying to form a References: field > for a reply that has multiple parents is discouraged and how to do so > is not defined in this document". You end up having References: which > has bunch of (thread-wise) random ids in random order instead of the > rfc-specified original, reply, replytoreply, etc. chain of ids. It's worth reading the top bit of http://www.jwz.org/doc/threading.html for what In-reply-to: and References: look like in practice. (Basically: a mess, and the references: header in particular can be truncated in any way that any MUA feels is reasonable.) The threading used by the Ferret indexer is a pretty faithful reproduction of the algorithm described on that page. I'm not that familiar with the one used by the Xapian index, but a cursory examination suggests it's a little more fragile. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel