| Summary | Multi-threaded Horde_Imap_Client |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | slusarz (at) horde (dot) org |
| Created | 12/21/2012 (4697 days ago) |
| Due | |
| Updated | 10/15/2013 (4399 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
Assigned to Michael Slusarz
This will have to wait until at least Horde_Imap_Client 3. I hope to
have it architectured in a way that we could possibly have BOTH
options by separating server processing from network protocol stuff
(reading/parsing).
http://www.php.net/manual/en/intro.ev.php
State ⇒ Accepted
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Multi-threaded Horde_Imap_Client
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
multi-threaded, using pthreads.
Move socket connection code to a separate thread, so that we can do
things like tokenize incoming stream and build objects while waiting
for the IMAP server to finish processing/sending data.