[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         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Horde_Imap_Client_Data_Thread getRawData()
  Queue              | Horde Framework Packages
  Type               | Enhancement
  State              | Rejected
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2019-09-17 02:20) wrote:


> getThread() requires UID.

For the record, it could also be a sequence number. It depends on the  
options passed to Horde_Imap_Client_Base::thread().

> So first I've got to fetch all messages to get UIDs, then fetch  
> threads one by one.

Not sure what you mean by you have to fetch all messages to get UIDs.  
You shouldn't have to fetch anything else from the server after the  
call to $imapOb->thread() to get UUIDs.  
Horde_Imap_Client_Data_Thread::messageList() will return the (sorted)  
list of all UUIDs that matched the search option in the thread() call.  
While this list doesn't give you the thread structure, it would be  
fairly easy to construct it by iterating once through the messageList().

Not sure exactly what your use case is here for having access to the  
entire mailbox's thread sort like this, but I can see where they may  
be some value in having that data exposed. I'd consider a patch that  
outputs this as a more formal structure.