[RCD] [PATCH] Threaded messagelist view patch rev5 (against r3022)

Chris January chris at atomice.net
Wed Oct 7 13:06:24 CEST 2009

On Wed, 07 Oct 2009 12:39:27 +0200, "A.L.E.C" <alec at alec.pl> wrote:
> Chris January wrote:
>> I just looked at what KMail does. It has both a Date column (for date
>> first message in thread) and Most Recent Date column (for date of most
>> recent message in thread). Perhaps that's the way to go?
> As I understand the first it's for ORDEREDSUBJECT and the letter for 
> REFERENCES. If we need both we just should add an (working) option to 
> change this behaviour. I think we don't need this (at least now) and we 
> should just use default THREAD command sorting. Also probably not every 
> server supports both.

KMail does its own threading, it doesn't use the IMAP THREADS command as
far as I know.
Sorting by Date is equivalent to THREAD=REFERENCES and sorting by Most
Recent Date is equivalent to THREAD=REFS.

>> Sorting by anything but the default order (i.e. index_sort=true) is
>> incredibly slow with 30,000 or so messages.
> THREAD command returns messages (threads) sorted by date, it's not 
> possible to speed this up. Index_sort option will not help and we have 
> two possibilities:
> - re-sort by root message index if index_sort=true,
> - forget about index_sort option when using threads

This is why there is a 'default' sort order in the threading patch. The
THREAD command returns, as you say, messages sorted by date. Roundcube then
sorts them again which can be very slow with lots of messages. So the
threading patch introduces the 'default' sort order, which could be better
called the 'unsorted' sort order, i.e. the messages aren't sorted at all
but kept in the same order they are returned by the server.


List info: http://lists.roundcube.net/dev/

More information about the Dev mailing list