Re: Re: HTTP_Request2
| From: | David Jean Louis | Date: | Tue, 28 Oct 2008 21:40:29 +0000 |
| Subject: | Re: Re: HTTP_Request2 | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-50957@lists.php.net to get a copy of this message | ||
Joshua Eichorn a écrit :
David Jean Louis wrote:The problem is that even if you use curl, you'll get memory limit problems. Yes, php is slow, but if you want to handle, say a 1 go response, you'll have to write your own curl read callback function *in php*, so where's the problem ? what does curl solves here ? parsing headers ? this is insignificant.Alexey Borzov a écrit :Handling all the processing in php is slow and uses more memoryTheir code suffers from the same problem as was described here, it is quite difficult to adapt it to using the cURL extension (or any other extension, for that matter). Note that they only provide socket-based backend.Again, why do we need "adapters" ? sorry but I just don't get it. It makes sense for a db package but here... Sockets are fine, shipped by default and available on any platform you can imagine.
Sockets don't do sslhuh ?! are you joking ? -- David