Re: [RFC] [VOTE] pecl_http
| From: | Andrea Faulds | Date: | Wed, 28 Jan 2015 20:56:50 +0000 |
| Subject: | Re: [RFC] [VOTE] pecl_http | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-81340@lists.php.net to get a copy of this message | ||
Hey everyone,
> On 28 Jan 2015, at 20:46, Matteo Beccati <php@beccati.com> wrote:
>
> Since PSR-7 is being discussed now *and* pecl_http can't implement an interface that still
> is being discussed, I would rather vote "no" now and maybe change my mind in future if
> PSR-7 becomes a thing and pecl_http follows. Or PSR-7 fails, for that matter.
Related to this: is it even possible for an internal class to rely on and formally, explicitly
“implement” a userland interface? It’s all very well if PHP has a built-in implementation that
follows PSR-7, but it would suck if you couldn’t pass an instance of that class to a function with
a (hypothetical) psr7\HttpMessage type hint.
Userland libraries don’t have this issue: they all just require the PSR-7 interface package in
their composer.json and all is well.
--
Andrea Faulds
http://ajf.me/