Tickets :: [#11373] Smarter determination of "next" message

6.0.0-beta1

7/9/25

Summary	Smarter determination of "next" message
Queue	IMP
Queue Version	Git develop
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	08/23/2012 (4703 days ago)
Due
Updated	08/29/2012 (4697 days ago)
Assigned
Resolved	08/23/2012 (4703 days ago)
Milestone
Patch	No

08/29/2012 12:48:56 PM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit 9a8e52151796ae099e59de76ec0fc538b0e2d7be Author: Michael M Slusarz <slusarz@horde.org> Date: Thu Aug 23 14:54:34 2012 -0600 ~~Request #11373~~: Improvements to pref-fetching algorithm Fetch both the previous and next unseen message. Fetch in all polled mailboxes, not just INBOX. imp/docs/CHANGES \| 2 +- imp/js/dimpbase.js \| 15 ++++++--------- imp/package.xml \| 2 +- 3 files changed, 8 insertions(+), 11 deletions(-) http://git.horde.org/horde-git/-/commit/9a8e52151796ae099e59de76ec0fc538b0e2d7be

08/23/2012 08:56:40 PM	Michael Slusarz	Assigned to Michael Slusarz State ⇒ Resolved

08/23/2012 08:56:04 PM	Git Commit	Comment #4	Reply to this comment
Changes have been made in Git (develop): commit 9a8e52151796ae099e59de76ec0fc538b0e2d7be Author: Michael M Slusarz <slusarz@horde.org> Date: Thu Aug 23 14:54:34 2012 -0600 ~~Request #11373~~: Improvements to pref-fetching algorithm Fetch both the previous and next unseen message. Fetch in all polled mailboxes, not just INBOX. imp/docs/CHANGES \| 2 +- imp/js/dimpbase.js \| 15 ++++++--------- imp/package.xml \| 2 +- 3 files changed, 8 insertions(+), 11 deletions(-) http://git.horde.org/horde-git/-/commit/9a8e52151796ae099e59de76ec0fc538b0e2d7be

08/23/2012 08:11:37 PM	Jan Schneider	Comment #3	Reply to this comment
Agreed to both.

08/23/2012 07:53:05 PM	Michael Slusarz	Comment #2	Reply to this comment
Or, even better, to download the first unseen message above and below the current message. I'm also thinking that we could extend the pre-fetching to any mailbox that is marked as polled. This is a reasonable compromise since the user has indicated that this is a mailbox where he/she expects to receive new (unseen) messages.

08/23/2012 09:04:36 AM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Smarter determination of "next" message Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Accepted	Reply to this comment
Prefetching the "next" message in IMP 6 is a nice feature that makes the interface feel much faster. Unfortunately it only works if you read messages from top to bottom. This is not always the case. A common scenario is to sort the messages from newest to oldest, but start reading from the oldest unread message and go up through the list. It would be smarter if the "next" message is determined at least by the sort order, if not by the way the user currently moves through the message list, i.e. if he navigated one message up, prefetch the 2nd next message up and vice versa.