On 30/01/15 15:08, Ferenc Kovacs wrote: > > > On Fri, Jan 30, 2015 at 2:45 PM, Michael Wallner <m...@php.net > <mailto:m...@php.net>> wrote: > >> https://wiki.php.net/rfc/pecl_http
> hi, > > just a small question: what will be the upgrade path for existing > pecl_http users upgrading to 7.0? I'd consider PHP7's http extension a new major version, i.e. v3. > 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 <http://pecl.php.net>, but I think that would > be a PITA for everybody). I definitley would stay away from having a separate PHP7 compatible PECL version, but coming v2 releases could take measures to prepare any transition to the PHP7 API. > ofc. this isn't a blocker problem, but something we should keep in mind. Alas, not much has changed so far: - no automatic json_decode() into $_POST: I doubt anybody used that - default etag hash algo for dynamic response bodies has changed to sha1 from crc32 and cannot be changed through an INI setting etags on dynamic content are, well, subject to change anyway, so I don't see major troubles - missing http\QueryString::xlate() This is a real BC break, though. -- Regards, Mike -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
