TCP dying

BlitzPlus Forums/BlitzPlus Programming/TCP dying

Regular K(Posted 2005) [#1]
Ive been making an online game that uses TCP for the internet protocol and well, its been working fine. It uses of course, server - client structure. But lately, the clients can connect, but after sending their first message, they die! My client works, and their clients have worked in the past.

Im wondering if theres any known problems with TCP, that well, causes it to die?


WolRon(Posted 2005) [#2]
Excuse me, but how can a client "DIE"?

What is DIE supposed to mean? Please be more specific. Maybe try posting some code...

Vague questions receive vague answers.


Regular K(Posted 2005) [#3]
It doesnt matter any more, I switched to UDP.

But ill just explain it a bit more then, the client would connect successfully, then send one message, then, it wouldnt be able to receive or send any more.


MagicalTux(Posted 2005) [#4]
I already experienced that when calling the read function a lot ...

Just use ReadAvail() in that case :)


Jono(Posted 2005) [#5]
A connection 'dying' is a very good term to use when refering to the loss of a signal. I understood exactly what you were talking about. Even if you did sort your problem out already. :D


Wings(Posted 2005) [#6]
Yah old UDP protocol still rulze games :)
its the verry easy to use..
"NEW" tcp is some kind of hard to use for beginners.