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
