On Sun, 16 Jan 2005, Alexander Krasnostavsky wrote:

Thanks for your fast response!

> 2. You are right about the case of both source and target is the same
> server. Therefore I recommend add indicators for source and target to
> distinguish between them.

Yes, that's what I'd like as well! I didn't figure out a quick and easy way to
make this though.

> To make 3rd party transfer work, FTP server must support this mode,

I don't think my problems to get it to work is related to the server, since I
got more basic errors.

If you apply the attached patch against a reasonably recent curl source code,
can you show me how you transfer a file (say "tmp/file-source") to another
location (say "tmp/file-dest") using the command line tool?

All new 3rd party options are named --3rd* something (for now).

> 3. I didn't find any example in RFC documents of using 3rd party transfer in
> URL.

I don't think 3rd party transfers are addressed in the URL specs.

> Therefore it depends on you to decide how URL will be defined to have both
> servers in it.

No, I meant that the source data could be in a separate URL exactly like the
target data already is today: "ftp://source-server.com/file/path".

> Another way, I didn't think before, is to define SOURCE_URL additionally to
> URL

Yes, that's the way I was trying to explain... :-)

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