Re: Re: HTTP_Request2

David Jean Louis wrote:

Joshua Eichorn a écrit :

David Jean Louis wrote:

Alexey Borzov a écrit :

Their 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.

Handling all the processing in php is slow and uses more memory

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.

Sockets don't do ssl

huh ?! are you joking ? -- David From the manual:

The /ssl:/// and /tls:/// transports (available only when openssl support is compiled into PHP) No opensls no ssl support. And curl does allow you to download files larger without a callback function, you just have to give it a file pointer. -josh