🚀 go-pugleaf

Dear Mark,

Thank you very much for your advice. It seems it solved my problem. I tried
with a block of 2048 bytes and it passed easily the point where my program
was timing out. Almost every time before it was blocking at the end of the
same file.
I was thinking if that block isn't too big (32 KB) and I tried with 16KB.
And just before your message I decided to reduce it to 8KB, but it still
timed out. Eventually maybe I would have decreased it even lower, but I
didn't think this will solve the problem...

And now the program just finished transferring all the files for the very
first time :-)

Best wishes to everybody,
Nicolae




"Mark Jacobs" <markj atty critical dotty co dotty uk> wrote in message
news:40f6a51a@newsgroups.borland.com...
> It may be that your block upload size is too big. I am not well-versed in
the
> FTP protocol, but in TCP/IP you are best advised to keep blocks at around
2048
> bytes tops. More preferable is a block size of 512 bytes. I think it takes
> longer (and is more dodgy) to get an acknowledgement of the transfer of a
> block as big as 16K, or the ACK is being lost at the end because the last
> block smothered it. This is only a guess, but since it is so easy to
change
> the block size in Indy, can you let us know what happens with 512 bytes
> instead of your 16K? TIA,
> -- 
> Mark Jacobs
> DK Computing
> http://www.dkcomputing.co.uk
> markj atty critical dotty co dotty uk
>
>