[Tickets #14943] Re: Horde_Imap_Client_Data_Thread getRawData()

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14943
------------------------------------------------------------------------------
  Ticket             | 14943
  Updated By         | mariusz.goch at spacja.com
  Summary            | Horde_Imap_Client_Data_Thread getRawData()
  Queue              | Horde Framework Packages
  Type               | Enhancement
  State              | Rejected
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


mariusz.goch at spacja.com (2019-09-16 16:34) wrote:

I now it was removed but there is still no alternative.
When I want to show all threads there is now easy way.
getThread() requires UID. So first I've got to fetch all messages to  
get UIDs, then fetch threads one by one.
In this usage getThread() is really a performance issue because in  
each call it go through whole array.
In mailbox that has few thousand messages should I call few thousand  
times getThread() and any single time getThread() will search through  
whole cached array.
Instead getThread() there could be getThreads() that will return same  
structure for all threads.
If this would be acceptable I will be happy to provide a patch.