Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81429
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54CB8AED.8040803@php.net>
References: <DDA98D4F-2105-415A-B921-01A622091FA9@php.net>
	<FA3623B5-6D82-475C-9E44-02287137E912@php.net>
	<54CB8AED.8040803@php.net>
Date: Fri, 30 Jan 2015 15:08:59 +0100
Message-ID: <CAH-PCH76w96PSEs5GWVS-LZoMcK809dC92jm=v0+F9gyCFVuZQ@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e010d849e68b113050ddf25d2
Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] pecl_http
From: tyra3l@gmail.com (Ferenc Kovacs)

--089e010d849e68b113050ddf25d2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 30, 2015 at 2:45 PM, Michael Wallner <mike@php.net> wrote:

> On 29/01/15 21:25, Michael Wallner wrote:
> >
> >> On 29 01 2015, at 12:14, Michael Wallner <mike@php.net
> >> <mailto:mike@php.net>> wrote:
> >>
> >> Hi!
> >>
> >> I=E2=80=99ve rewritten the RFC for pecl_http and hopefully addressed m=
ost of
> >> the things mentioned previously.
> >>
> >> I you still find anything lacking, please let me know, so I can expand
> >> the RFC accordingly.
> >>
> >> And of course, everything else is up for discussion.
>
> Update:
>
> Removed optional dependencies on all three extensions (json, iconv,
> hash), and the one INI entry related to it. ETags of dynamic response
> bodies would now always be just sha1 hashes.
>
> https://wiki.php.net/rfc/pecl_http#dependencies
>
> --
> Regards,
> Mike
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
hi,

just a small question: what will be the upgrade path for existing pecl_http
users upgrading to 7.0?
if we would just move the current ext as is into php-src it would be no
problem for them, but based on the recent discussion that is unlikely and
if we change the userland api they will be forced to upgrade their code
(except if we are willing to provide a php7 compatible version of pecl_http
on pecl.php.net, but I think that would be a PITA for everybody).
ofc. this isn't a blocker problem, but something we should keep in mind.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--089e010d849e68b113050ddf25d2--