Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53041 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8586 invoked from network); 6 Jun 2011 16:25:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jun 2011 16:25:47 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-ww0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:57587] helo=mail-ww0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C1/62-23189-B8FFCED4 for ; Mon, 06 Jun 2011 12:25:47 -0400 Received: by wwd20 with SMTP id 20so3693004wwd.11 for ; Mon, 06 Jun 2011 09:25:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2pqhqorPNKOfwlf63ga4w0EFr5DvyO0ISDH/B7iFTJI=; b=YAsSkPHdeSKBVnRrHMuqTtmk2SPeN7TnGgLTFjntxZG7Xl4t0ikN6w0R4yWowA5tuJ b1x30jjbLFUpJ0eq5JUseE7FMl4H2G/XioGeKw8cB9sIHolmbxVJyfAyCSAeW1/saUTJ HAj3HasnFA34DllsVXF5v6JzXNUCjV1mGD+bs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=W05pRwCbPUdroIWICVw4WT2olLsAbZ6t2eup6roMZ/3fjL4Qn4dkPvarmBx+scZzBw eB9Kai4GKz6PE/50K+zsIDoboN7B+NW/C6ySPyUmVSu9lRGJMAkPXKGyXFRdyWBD7Oyx QMDtEUpqK8GXIkkDXSCdDTdrrm/8/XyQULCzo= MIME-Version: 1.0 Received: by 10.216.221.32 with SMTP id q32mr2583076wep.77.1307377543686; Mon, 06 Jun 2011 09:25:43 -0700 (PDT) Received: by 10.216.253.168 with HTTP; Mon, 6 Jun 2011 09:25:43 -0700 (PDT) In-Reply-To: <4DECEFBF.5070105@garfieldtech.com> References: <8757232E56758B42B2EE4F9D2CA019C901499F97@US-EX2.zend.net> <4DECEFBF.5070105@garfieldtech.com> Date: Mon, 6 Jun 2011 18:25:43 +0200 Message-ID: To: Larry Garfield Cc: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Bundling "modern" extensions From: pierre.php@gmail.com (Pierre Joye) On Mon, Jun 6, 2011 at 5:18 PM, Larry Garfield wro= te: > For me the question isn't "should we bundle memcached in PHP core", it's > "how do we establish an expected baseline of PHP components that develope= rs > can reasonably expect will be available, and what should be in that?" =A0= Right > now, that baseline is "bundled in core". Having memcached, mongodb or whatever other similar extensions in core won't make these hosters provide memcache or mongodb support, not the waste majority. However there are already hosters providing mongodb or couchdb support and they all take care of the respective extensions using the non core modules (pecl or github). That's why I really like to differentiate sqlite/http and similar extensions from extensions being a client for a given server or service. Mysql is still a de facto standard but that's something we cannot really compare to any of the current nosql&co technologies, from a usage or spread point of view. Dedicated hosting are usually the place where they are used (virtualized or not). Cheers, --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org