# [RFC] pecl_http - Thread: https://externals.io/message/76684 - Original archive: https://news-web.php.net/php.internals/76684 - Started by Michael Wallner on 2014-08-19T07:49:34+00:00 - Messages: 12 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #76684 — Michael Wallner — 2014-08-19T07:49:34+00:00 URL: https://externals.io/message/76684#76684 Hi PHP internals! I've created an RFC for discussion: Whether it is feasible to add pecl_http v2 to the core. https://wiki.php.net/rfc/pecl_http -- Regards, Mike --- ## #76689 — Jan Ehrhardt — 2014-08-19T09:17:04+00:00 URL: https://externals.io/message/76684#76689 · In reply to: #76684 Michael Wallner in php.internals (Tue, 19 Aug 2014 09:49:34 +0200): >Hi PHP internals! > >I've created an RFC for discussion: > > Whether it is feasible to add pecl_http v2 to the core. > >https://wiki.php.net/rfc/pecl_http Is pecl_http v2 still dependent on propro and raphf? If so, they should be in core as well. Jan --- ## #76692 — Pierre Joye — 2014-08-19T09:24:09+00:00 URL: https://externals.io/message/76684#76692 · In reply to: #76689 > Michael Wallner in php.internals (Tue, 19 Aug 2014 09:49:34 +0200): > > […] > > Is pecl_http v2 still dependent on propro and raphf? If so, they should > be in core as well. > I never really understood why they are needed or why they have been splitted off. I can imagine that other exts may need a similar thing but... Cheers, -- Pierre @pierrejoye | http://www.libgd.org --- ## #76699 — johannes@schlueters.de — 2014-08-19T11:53:14+00:00 URL: https://externals.io/message/76684#76699 · In reply to: #76684 > Hi PHP internals! > > I've created an RFC for discussion: > > Whether it is feasible to add pecl_http v2 to the core. > > https://wiki.php.net/rfc/pecl_http In my opinion when moving this to core the http(s):// stream should use the same HTTP implementation so one has consistent behavior. I also see that HTTP offers "Content type guessing [...] by building this extension with libmagic support" I think that should based on fileinfo so both report the same type for a file. Again consistency. I also think the HTTP module should be forced on (like SPL or pcre) or at least be on by default (unless --disable-[all|http] is used) johannes --- ## #76700 — Michael Wallner — 2014-08-19T12:18:40+00:00 URL: https://externals.io/message/76684#76700 · In reply to: #76689 > > Is pecl_http v2 still dependent on propro and raphf? If so, they should > be in core as well. > > Yes, they are mentioned in the "Open Issues" section. -- Regards, Mike --- ## #76701 — Michael Wallner — 2014-08-19T12:19:49+00:00 URL: https://externals.io/message/76684#76701 · In reply to: #76692 > > > […] > > I never really understood why they are needed or why they have been > splitted off. I can imagine that other exts may need a similar thing > but... > To be reusable. pecl/raphf is also used by pecl/pq; peck/propro has not had another use case yet, though. -- Regards, Mike --- ## #76702 — Michael Wallner — 2014-08-19T12:22:26+00:00 URL: https://externals.io/message/76684#76702 · In reply to: #76699 > > In my opinion when moving this to core the http(s):// stream should use > the same HTTP implementation so one has consistent behavior. > > This would add a hard dependency on libcurl, which I'd be obviously fine with. > I also see that HTTP offers "Content type guessing [...] by building > this extension with libmagic support" I think that should based on > fileinfo so both report the same type for a file. Again consistency. > This is from the v1-docs and was developed in a time before Fileinfo existed. That feature was not elevated to v2. > > I also think the HTTP module should be forced on (like SPL or pcre) or > at least be on by default (unless --disable-[all|http] is used) > > johannes > > -- Regards, Mike --- ## #76703 — Pierre Joye — 2014-08-19T12:29:59+00:00 URL: https://externals.io/message/76684#76703 · In reply to: #76701 > > > […] > > > To be reusable. pecl/raphf is also used by pecl/pq; peck/propro has not had > another use case yet, though. propo could be a spl thing, if usefull for other. As of raphf, not sure, mixed toughts. Maybe as part of main/? I am not sure I like to habe two other extensions for that, they are handy tho' :) -- Pierre @pierrejoye | http://www.libgd.org --- ## #76705 — Michael Wallner — 2014-08-19T13:17:35+00:00 URL: https://externals.io/message/76684#76705 · In reply to: #76684 > Hi PHP internals! > > I've created an RFC for discussion: > > Whether it is feasible to add pecl_http v2 to the core. > > https://wiki.php.net/rfc/pecl_http > Just a heads up. People seem very confused because they read the docs on php.net and don't bother to actually read the (very short) RFC, so here's a link to the API docs of v2; you're welcome. http://devel-m6w6.rhcloud.com/mdref/http/ -- Regards, Mike --- ## #79770 — Michael Wallner — 2014-12-17T10:26:37+00:00 URL: https://externals.io/message/76684#79770 · In reply to: #76684 > Hi PHP internals! > > I've created an RFC for discussion: > > Whether it is feasible to add pecl_http v2 to the core. > > https://wiki.php.net/rfc/pecl_http > Just a minor update: the two PECL depencies have been ported to ZE3. -- Regards, Mike --- ## #79800 — Pierre Joye — 2014-12-18T00:38:32+00:00 URL: https://externals.io/message/76684#79800 · In reply to: #79770 > > > > […] > > Just a minor update: the two PECL depencies have been ported to ZE3. > Btw, I still wonder if their features could be provided as part of php instead of having to add 3 exts. Thoughts? --- ## #79804 — Michael Wallner — 2014-12-18T11:45:37+00:00 URL: https://externals.io/message/76684#79804 · In reply to: #79800 > > On Dec 17, 2014 5:26 PM, "Michael Wallner" > wrote: > > […] > > Btw, I still wonder if their features could be provided as part of php > instead of having to add 3 exts. Thoughts? > I guess we could. pecl/propro was a replacement for the (then) disfunctional zend_object_proxy, which seemingly has completely gone in ZE3 except a dangling declaration in zend_objects_API.h. pecl/raphf sort of overlaps with zend_list API, though. -- Regards, Mike