On Wed, 19 May 2004, Alexander Krasnostavsky wrote:

> I checked in RFC documents and forums that describe url and found that
> there is no definition for the target. So there is no need to change the
> source url. For the target I think to add to structures the following
> definitions:

[struct modifications looking good]

> and the following options for curl_easy_setopt():
> CURLOPT_FTP_TARGET_HOST
> CURLOPT_FTP_TARGET_PORT
> CURLOPT_FTP_TARGET_USERPWD
> CURLOPT_FTP_TARGET_PATH

... they did invent the URL to supply all this info in one single string which
is why I suggest a CURLTOPT_FTP_TARGET_URL (or whatever the name would be)
that could provide all the four fields mentioned above. You're providing the
source data as a URL anyway. Or is there a point in offering it with multiple
options like this?

Using URL syntax for target would also make it possible to i.e use FTP to the
first site and FTPS to the second, which your options don't provide and why
not the ";type=X" thing ftp URLs offer...

-- 
     Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
      Dedicated custom curl help for hire: http://haxx.se/curl.html