I started that with the curlstreams, but libcurl just didn't really want to play nicely as a stream.
In addition, PHP kept on requiring the latest and greatest versions of libcurl for the curl extension; they are frequently not supported in stable binary distros and were hard to obtain (crappy SF.net hosting at that time). As a result, I stopped using ext/curl and libcurl and we're where we are today. Things might well be different now; if libcurl can be massaged in, thats great, but let's try and make it work really well or not bother with it. If the latter proves to be the case, I'm +1 on having a more advanced HTTP wrapper as a PECL extension; it can be loaded at run-time to override the basic wrapper. (openssl extension uses this trick to remap TCP transports, and IIRC, the curlstreams worked this way too). --Wez. On Wed, 8 Sep 2004 14:48:08 -0700 (PDT), Rasmus Lerdorf <[EMAIL PROTECTED]> wrote: > Why not integrate libcurl more intimately? I can see Sara's point in > wanting to be able to pipeline http streams, but re-inventing the wheel > doesn't seem like a good idea either. Get the streams code to use the > appropriate features in libcurl, if present. We should be able to solve > the problem without writing all this duplicate code. > > -Rasmus > > > > On Wed, 8 Sep 2004, Andi Gutmans wrote: > > > Yep I concur. No need to bloat the code base for no good reason. > > Whoever needs the flexibility you are talking of can use CURL. > > > > Andi > > > > At 12:29 PM 9/8/2004 -0700, Sterling Hughes wrote: > > > > Sacha- > > > > > > > > I can appreciate that there is a limited potential need for PHP to > > > support > > > > chunked encoding >right-now<, however this is one step in a larger process > > > > to support keep-alives and issuing multiple requests over a single > > > > http/https session. I'd like to work on the issues raised by Nuno: (A) > > > > being minor, and (B) being (seemingly) unrelated to chunked-encoding > > > itself. > > > > If the release cycle starts to approach and we're no better off then > > > > obviously this can and should be torn out in the name of stability. > > > > > >The reason I'm against these changes is that simple HTTP support is > > >fine, but when it comes to getting more complex support written by PHP > > >it makes very little sense to me to not use some external library > > >(e.g. cURL). Supporting these features properly, completely, with > > >multiple browsers is too large a code size to duplicate within PHP > > >itself, simple support is one thing, but I think its wrong to get more > > >advanced in this respect. > > > > > >_Sterling > > > > > >-- > > >PHP CVS Mailing List (http://www.php.net/) > > >To unsubscribe, visit: http://www.php.net/unsub.php > > > > -- > > PHP CVS Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > PHP CVS Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
