Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52905
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.160.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4DEAD511.2090408@lerdorf.com>
Date: Sat, 4 Jun 2011 18:09:50 -0700
Cc: Scott MacVicar <scott@macvicar.net>,
 "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <83708FB3-7D92-4E42-BB5A-79EDF1050CE9@roshambo.org>
References: <8757232E56758B42B2EE4F9D2CA019C901499F97@US-EX2.zend.net> <4DEAC668.9050902@sugarcrm.com> <31B6F2D7-3E22-4A85-B391-70C4F06F7364@macvicar.net> <4DEAD511.2090408@lerdorf.com>
To: Rasmus <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] Bundling "modern" extensions
From: philip@roshambo.org (Philip Olson)


On Jun 4, 2011, at 6:00 PM, Rasmus wrote:

> On 06/04/2011 09:03 PM, Scott MacVicar wrote:
>> On Jun 4, 2011, at 4:57 PM, Stas Malyshev wrote:
>>=20
>>> 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.
>>=20
>> OAuth is basically outdated now, OAuth2 is going through the final =
IETF certification steps. No real technical changes in the last few =
drafts.
>=20
> And OAuth2 is simple enough that an extension really isn't needed for
> it. OAuth1 was painful and the extension helped a lot. But all the
> painful bits that the extension takes care of are gone in OAuth2.

Ideas for how and where to document PHP+OAuth2? Like, should we keep =
ext/oauth documented as is but expand it to include plenty of OAuth2 =
information? That may be confusing... hmmm....

Regards,
Philip=