TCP acks when packets have been received, this is how blocking sockets know when to return from blocking during a data write. Or to send events that data has been successfully acked by the end server.
If an end server or mid router (for example, a wifi connection) is getting overloaded it will start dropping packets which will cause your program to resend.. and in the case of a blocking stream, to continue blocking. UDP, which Flash doesn't support as far as I know, just dumps the packets on the wire and hopes for the best. But that's for another discussion entirely. --- In [email protected], Weyert de Boer <[EMAIL PROTECTED]> wrote: > > Hmm, as far as I know you can't really control such things with TCP > sockets in general. I mean the TCP(/IP) itself doesn't enable to force > sending the bytes from the buffer. It makes it own decision what and > when to send stuff. I wants to send the stuff as efficient as possible. > > No, I have to admit I am not really sure about this. You might want to > look up about the TCP protocol, Nagle algorithm etc. > > > Yours, > Weyert >
