Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69989 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69883 invoked from network); 31 Oct 2013 23:12:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Oct 2013 23:12:41 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.123 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.123 smtp123.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.123] ([108.166.43.123:42762] helo=smtp123.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/20-02760-8E3E2725 for ; Thu, 31 Oct 2013 18:12:40 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7545D1A026A; Thu, 31 Oct 2013 19:12:37 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp8.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 26DB01A02A9; Thu, 31 Oct 2013 19:12:37 -0400 (EDT) Message-ID: <5272E3E4.5030907@sugarcrm.com> Date: Thu, 31 Oct 2013 16:12:36 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Christopher Jones , PHP internals References: <526ACC9B.4090204@oracle.com> <5272C51F.7090106@oracle.com> In-Reply-To: <5272C51F.7090106@oracle.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Adding new MIME types for the CLI web server From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Final comments anyone, before I commit next week? It looks strange that we have to hardcode so many mimetypes in the code, and doesn't sound a scalable solution. Can't we make it use data from fileinfo or some other customizeable table so we don't have to keep all MIME types hardcoded in the code? Maybe some ability to use Apache's mime.types file? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227