> mmm, hold on
>
> what if user does a 'default' transfer with a relative path. libcurl will
> CWD into that path and do the transfer. Then the user does another
> transfer with a relative path, but specifying CURLFTPMETHOD_NOCWD. libcurl
> should CWD back to the entry path and then perform the full path.
>
> But the user specified CURLFTPMETHOD_NOCWD, should libcurl then CWD back
> to the entrypath ?? Or can we refuse to change the CURLOPT_FTP_FILEMETHOD
> between subsequent transfers ?
>
> Immanuel
>

no, that would require the user to know what libcurl does exactly. Or he
should actively disable connection re-use

So maybe it would be best to return to the entry path right after (within)
a transfer which just CWDed into the path, rather then before a subsequent
transfer ?
Received on 2007-09-27