Jump to content

View more

Image of the Day

雑魚は多めにして、爽快感重視にしつつ・・・(´・ω・`)
早いとこ、ベースを作って、完成にもっていかないとね。
タイトルもまだ迷ってるだよなぁ。 
#indiedev  #indiegame #screenshotsaturday https://t.co/IwVbswGrhe
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Connection flood problems?

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
4 replies to this topic

#1 Starfall   Members   

122
Like
Likes
Like

Posted 28 April 2000 - 07:55 AM

I am running a TCP connection which will need to be sending large chunks of data infrequently. I have a buffering system so that if the TCP buffer becomes full the data will be stored until it can properly be sent. However, my question is, what happens if the sender''s connection is much faster than the receiver''s? I assume this would result in the receiver getting flooded, unless TCP has some way of dealing with it automatically? If not, what measures can I take to avoid the problem? I can see that one solution would be to allow the client to define a data rate, but then there''s the question of making that rate optimal... and if the rate was too high, the connection might begin to flood? If anyone can point me in the right direction here I''d greatly appreciate it. Also, if anyone can recommend a book that deals with these sort of issues, I''d be most interested to hear about it. Thanks! Starfall

#2 SiCrane   Moderators   

11762
Like
Likes
Like

Posted 28 April 2000 - 09:15 AM

This isn''t a detail you need to worry about under TCP. TCP automatically throttles back transmissions when packet loss is signalled (or an ICMP source quench message is sent). So the average transmission rate that your sender will transmit will be at about 75% the rate that the receiver can receive. Or if the bottleneck is somewhere in between, about 75% of that.

#3 Cloxs   Members   

122
Like
Likes
Like

Posted 28 April 2000 - 09:29 AM

Yeah, SiCrane is right TCP is really reliable. If you were using UDP you''d have a problem (I think), but in any case if you make the reciever''s window large enough, you wouldn''t have a problem.

#4 Starfall   Members   

122
Like
Likes
Like

Posted 28 April 2000 - 07:32 PM

Thanks very much SiCrane. I figured there could be something like that in TCP, given all the other things that it controls for the connection, but was unsure as to how it would operate. Should save me messing around with such things anyway. Is that knowledge a result of personal experience, or is there a good information source for such networking questions?

Starfall

#5 Starfall   Members   

122
Like
Likes
Like

Posted 28 April 2000 - 08:19 PM

Another question. Say I send some data on a non-blocking socket, and immediately call closesocket on that socket. If the data has not already been sent at the time the socket is "closed", is that data ignored, and the socket closed, or is all the data sent before the socket is actually removed?

Thanks again.

Starfall




Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.