Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52900 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46915 invoked from network); 5 Jun 2011 00:03:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2011 00:03:27 -0000 Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 209.85.210.42 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 209.85.210.42 mail-pz0-f42.google.com Received: from [209.85.210.42] ([209.85.210.42:51840] helo=mail-pz0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/39-14012-EC7CAED4 for ; Sat, 04 Jun 2011 20:03:27 -0400 Received: by pzk37 with SMTP id 37so1417413pzk.29 for ; Sat, 04 Jun 2011 17:03:23 -0700 (PDT) Received: by 10.68.1.103 with SMTP id 7mr1415519pbl.81.1307232203553; Sat, 04 Jun 2011 17:03:23 -0700 (PDT) Received: from [10.0.1.103] (adsl-76-228-82-246.dsl.pltn13.sbcglobal.net [76.228.82.246]) by mx.google.com with ESMTPS id k9sm2541695pbc.86.2011.06.04.17.03.21 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 04 Jun 2011 17:03:23 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii In-Reply-To: <4DEAC668.9050902@sugarcrm.com> Date: Sat, 4 Jun 2011 17:03:02 -0700 Cc: Andi Gutmans , "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <31B6F2D7-3E22-4A85-B391-70C4F06F7364@macvicar.net> References: <8757232E56758B42B2EE4F9D2CA019C901499F97@US-EX2.zend.net> <4DEAC668.9050902@sugarcrm.com> To: Stas Malyshev X-Mailer: Apple Mail (2.1084) Subject: Re: [PHP-DEV] Bundling "modern" extensions From: scott@macvicar.net (Scott MacVicar) On Jun 4, 2011, at 4:57 PM, Stas Malyshev wrote: > Hi! >=20 >> In parallel I'd also see if there are any key extensions which we >> think are mainstream, stable and well maintained enough to be >> included. For example, http comes to mind. >=20 > Maybe also oauth? It's getting popular and widely used. OAuth is basically outdated now, OAuth2 is going through the final IETF = certification steps. No real technical changes in the last few drafts. - S