> I have found that if I call TypeBinaryAsync first
> and then in the Request event (ftpTypeSetAsync) I now call GetAsync
You only need to set type once, and if you are using Async events then
OnRequestDone is where you check your state mechanism for the next
command. Personally, I mostly use th
I think you are correct. I have found that if I call TypeBinaryAsync first
and then in the Request event (ftpTypeSetAsync) I now call GetAsync then it
works.
Is this the best way to do it?
I guess I thought that just setting Binary to TRUE, it was going to send the
TYPE I automatically.
Graham
> The problem is that for every carriage return I get an additional
> non-Unicode carriage return.
> The ICS FTP Client component has the "Binary" property set TRUE.
But are you calling the TypeBinary or TypeSet methods that actually send
the TYPE command?
Angus
--
To unsubscribe or change you
So now I have another issue which I'm sure someone will know the answer to.
I am copying Unicode files from my FTP server to a local directory. The
problem is that for every carriage return I get an additional non-Unicode
carriage return. So for a CR LF where I should receive 0D 00 0A 00, I get 0D
> I am using THttpConnection.AnswerString from file
> OverbyteIcsHttpSrv and want to send several answers in a long
> running request via transfer-encoding "chunked".
> What do I have to do for this to be possible?
Not sure, I tried to add an automatically refreshing push page to my ICS
web appl
