Hi Daniel,

In PHP, we have lived without writeable http for a long time now, so
this was not actually something I was worried about :-)
However, I think that you can "leverage" (that's the corporate word
for "borrow from" ;-) PHP and Apache to help with the chunked transfer
(and also zlib/deflate handling).

I've got some thoughts on cookies and "sessions" and how they can be
tied into the framework that I've developed for PHP that might benefit
other applications adopting libcurl in a similar way: PHP will have
a "stream context", functionally somewhat similar to an "internet session"
in the Windows Inet API. The plan is to have common settings, cookies
and other session related information stored in this context parameter.

From what I've read so far from the various docs in the curl CVS,
although curl can do this stuff, it's not 100% application friendly.
For instance, with the cookie jar functionality, I'd like to be able
to specify callbacks for reading individual cookies from the jar and
writing them to the jar. Then we can implement the jar using a PHP
hash table, which means that scripts can directly manipulate it
(which = very nice indeed).

--Wez.

On 12/08/02, "Daniel Stenberg" <daniel_at_haxx.se> wrote:
> Hey
>
> It just struck me that when you're adding a proper write-to-url feature to
> PHP built on curl, I'd suggest that we have a go at finally implemented
> chunked-encoded transfers for upload, as otherwise the writing will be a bit
> limited.
>
> Just a thought.

-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
Received on 2002-08-13