🚀 go-pugleaf

"Paul at NCF" <notplmacca@clara.co.uk> wrote in message
news:45d83fd9$1@newsgroups.borland.com...

> In the IdFTPServerAfterUserLogin handler I set the directories as
> follows (I presume this is ok, or should be doing this some other
way):

You are using DOS-style path delimiters, but TIdFTPServer defalts to
Unix-style delimiters instead.  That has a big influence on
TIdFTPServer's behavior.  You can't mix the two together.

If you are using Indy 10, then I suggest you attach a TIdFTPFileSystem
instead of trying to parse everything yourself manually.

> In the IdFTPServerListDirectory handler I print out the home,
current, and
> parameter APath.  The APath seems to be rubbish, or has something
appended.
> I'm emulating DOS and the component properties seem to indicate this
is in
> use.  Am I missing something or is this a known problem?

Since you did not show any of your code, there is no way to diagnose
your problem.

> The ListDirectory does this, what is the Copy function doing?

Comparing the last character in the string to the specified path
delimiter.

> where is the client IP connection data recorded, I can't see it in
the
> TIdFTPServerThread *ASender and TIdPeerThread *AThread parameters?

TIdPeerThread.Connection.Socket.Binding.PeerIP


Gambit