🚀 go-pugleaf

May I just clarify why I gave that advice. I have been streaming sound over
TCP/IP recently, and using Client and Server Sockets (the ones that come with
BCB5 on the Internet tab). I found that the larger I made the packets I was
sending through ServerSocket1, the longer the delays and the worse the
reliability of delivery. I agree with Remy that this should *NOT* be
happening, and that TCP/IP is supposed to guarantee delivery or an error,
whatever the packet size. But there is a substrate that underlies the TCP/IP
protocol, and that is the network layer. Perhaps under Windows OS, this layer
is limited to a certain packet size before reliability is compromised. Who
knows?!? In my experiments, I found that 2048 is fine for transfers across
LANS and 512 is great for Internet transfers. Indy probably does chop the
output buffer up to send it out, but the minimum packet size is wrongly
calculated. Sure TCP/IP will report it can handle 16K chunks, but it won't
reliably in reality. Setting a smaller ftp buffer size in Indy means that the
socket send buffer Indy uses can be only as big as the specified buffer size.
and this, I think, has cured the problem.

Glad it sorted your problem out, Nicolae. I reckon that it shouldn't slow your
transfers down at all - it may even speed them up, because there are less
packets having to be re-sent.
-- 
Mark Jacobs
DK Computing
http://www.dkcomputing.co.uk
markj atty critical dotty co dotty uk


"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> wrote in message
news:40f6cbe5$1@newsgroups.borland.com...
|
| "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.
|
| That has nothing to do with it.  Block size does not matter to Indy at all,
| since every byte received is buffered in memory regardless of the block size
| used.  Indy reads however many bytes are actually available in the socket.
| If Put() is waiting for a response from the server that never comes, then
| the server is not sending the response to begin with, or it is somehow
| getting lost during transmission altogether.