| Summary | Imap_Client: Add unix socket support |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Enhancement |
| State | Assigned |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 08/22/2013 (4453 days ago) |
| Due | |
| Updated | 08/26/2013 (4449 days ago) |
| Assigned | 08/26/2013 (4449 days ago) |
| Resolved | |
| Milestone | Horde_Imap_Client 3.0 |
| Patch | No |
State ⇒ Assigned
Milestone ⇒ Horde_Imap_Client 3.0
for this in my local repository, that part of the code is unlikely to
change much.
This is such a special-use case, I don't want to have to
document/support this directly in the Horde_Imap_Client_Base
constructor. I'd rather allow something like supporting the base tcp
connection like we already do (since it is what is needed 99% of the
time), and allow a way to pass in a pre-configured object to be
directly used as the connection to support the special 1% of other use
cases.
Priority ⇒ 1. Low
New Attachment: 0001-Add-unix-socket-support.patch
Patch ⇒ No
Milestone ⇒
Summary ⇒ Imap_Client: Add unix socket support
Type ⇒ Enhancement
State ⇒ New
Queue ⇒ Horde Framework Packages
for administrative purposes I run a cyrus imapd "admin" instance
accessible via a unix socket only.
Attached patch adds support for unix sockets to Horde_Imap_Client.
It's activated when you use 'unix' as port.
Let me know what you think. I didn't document
it yet since I first want to know if mms gives the green light for this.
Thomas