I need some input on the following cookie issues.

Back in June [1], we discussed around the need for a more advanced cookie
parsing and storing in curl - the 'cookie jar' concept.

Briefly, this would imply that curl should be able to store cookies, not only
cookies that were just received from a remote server (as it can save today
using the dump-header option), but the combined result of previously read
cookies and the newly received ones.

I've added code that know how to dump all cookies in a (Netscape formatted)
file, which seems to be working fine.

Now, previously when we discussed this matter we talked about a few issues
regarding all this, and now I need to re-ventilate them and make descisions
based on your responses:

 1. File locking. It was said we need file locking to have several invoked
    curls all write to the same destination file. I have serious doubts
    around this. Not only do I suspect that people will still make mistakes
    when using a single output file, but we'll also get problems with systems
    that don't do proper locking (like various OSes or just systems running
    on NFS or similar).

 2. Cookie filtering. Are we gonna support that somehow? How would one want
    to filter cookies? On sending and/or receving cookies?

I need your views on this!

[1] = The mailing list thread can be read from here
      http://curl.haxx.se/mail/archive-2001-06/0092.html

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/