Hi, this may be a bit late:
On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote :
> * allowing "persistent" cURL handles that survive the request, for HTTP
> 1.1 persistent connections
Why only for persistent HTTP/1.1 connection and not other
type of curl resources like F
At 07:14 10/22/2002 +0200, Andi Gutmans wrote:
Well, the reason for the generator, is it will build an extension that
mimics the current version of cURL installed which will allow the cURL
extension to support multiple versions of the library without a lot of
maintanence and stuff :)
Don't forg
At 01:54 AM 10/22/2002 +0200, Sterling Hughes wrote:
On Tue, 2002-10-22 at 01:38, Alan Knowles wrote:
> Non blocking connections would be nice...
>
> - On the generating stuff - why do you want to generate the code on the
> users system? -
> all the re2c stuff in CVS is 'pre-genereated'
>
> It wou
Sterling Hughes wrote:
On Tue, 2002-10-22 at 01:38, Alan Knowles wrote:
Non blocking connections would be nice...
- On the generating stuff - why do you want to generate the code on the
users system? -
all the re2c stuff in CVS is 'pre-genereated'
It would be nice to have extension generator
On Tue, 2002-10-22 at 01:38, Alan Knowles wrote:
> Non blocking connections would be nice...
>
> - On the generating stuff - why do you want to generate the code on the
> users system? -
> all the re2c stuff in CVS is 'pre-genereated'
>
> It would be nice to have extension generator that could b
Non blocking connections would be nice...
- On the generating stuff - why do you want to generate the code on the
users system? -
all the re2c stuff in CVS is 'pre-genereated'
It would be nice to have extension generator that could be built upon,
that didnt involve re-reading all those perl/awk
On Mon, Oct 21, 2002 at 10:52:10PM +0200, Sterling Hughes wrote:
> > > Well, currently i plan on using a Perl script to read the curl.h
> > > definition file, and generate the code for all options that don't meet
> > > the following criterium:
> >
> > What, you can't write a simple parser in php?
On Mon, 2002-10-21 at 22:46, Shane Caraveo wrote:
> Sterling Hughes wrote:
> > On Mon, 2002-10-21 at 22:15, Jon Parise wrote:
> >
> >>On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote:
> >>
> >>
> >>>* Autogenerating much of the interface between cURL and PHP, allowing
> >>>PHP to su
Sterling Hughes wrote:
On Mon, 2002-10-21 at 22:15, Jon Parise wrote:
On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote:
* Autogenerating much of the interface between cURL and PHP, allowing
PHP to support multiple versions of the underlying cURL library
By what mechanism do y
On Mon, 2002-10-21 at 22:15, Jon Parise wrote:
> On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote:
>
> > * Autogenerating much of the interface between cURL and PHP, allowing
> > PHP to support multiple versions of the underlying cURL library
>
> By what mechanism do you plan on im
On Mon, Oct 21, 2002 at 10:12:55PM +0200, Sterling Hughes wrote:
> * Autogenerating much of the interface between cURL and PHP, allowing
> PHP to support multiple versions of the underlying cURL library
By what mechanism do you plan on implementing this?
--
Jon Parise ([EMAIL PROTECTED]) :: The
Hi,
I'm going to be working on updating the PHP cURL extension in the coming
weeks:
* adding the multi-interface.
* ssl session id caching (globally)
* global dns cache in threaded webservers (same for ssl sesssion id
caching)
* allowing cURL handle re-use.
* allowing "persistent" cURL handles
12 matches
Mail list logo
