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

So your suggestion is to add CURLTOPT_FTP_TARGET_URL additional to the 4
option for setopt(). I am not complete with FTP and FTPS or ";type=X"
because the data connection is between the remote host and the options
should be consistent, i.e. if for the first URL ";type=X" and for the
second - ";type=Y", we have inconsistency. Therefore it is better that
such kind of options will be defined only, let's say, for the source URL
and CURLTOPT_FTP_TARGET_URL will not exist. And also FTP or FTPS will
defined once according to the source URL, which means that the data
connection between remote hosts will be the same.

The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated recipient(s)
of the message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or copying of
this communication is strictly prohibited and may be unlawful.
If you have received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you.
Received on 2004-05-19