Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28339 invoked from network); 27 Apr 2012 17:47:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Apr 2012 17:47:35 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.113 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.113 smtp113.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.113] ([67.192.241.113:43257] helo=smtp113.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/E1-16466-5BBDA9F4 for ; Fri, 27 Apr 2012 13:47:34 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp21.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 03E612407C6; Fri, 27 Apr 2012 13:47:30 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp21.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id B05EE24054C; Fri, 27 Apr 2012 13:47:29 -0400 (EDT) Message-ID: <4F9ADBB1.1040006@sugarcrm.com> Date: Fri, 27 Apr 2012 10:47:29 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Pierre Joye CC: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] considering to remove ext/imap from master From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Before I go with a RFC and all that, I would like to check the current > feeling about killing ext/imap. The c-client project is dead since > quite some time already. I do not see any viable alternative > (applicable to server side usages) and it would be very hard to > maintain the same APIs, given the little mess in the imap's API. Whatever mess it is, tons of code is using it, and isn't going to move to Zend Framework any time soon (and roundcube is GPL which means it's unusable for many projects). So dropping it means these projects will never be able to upgrade. Now, what would such move give us? Is there any problem with imap now? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227