how to convert to UDP

[Dnsgm]

What exactly is the difference between a UDP connection and a TCP/IP connection?

How do I know which one I'm using? and how do I convert to UDP if I'm using TCP?

 

[DJ-CHRIS1]

UDP just sends a packet, and hopes it's recieved, their is no conformation that is recieved.

TCP open a connections and checks to see if the packet arrived. Their's a good explination wikipedia.

 

[bilbus]

you cant convert it .. just does not work that way.

 

[Dnsgm]

lets say taht im making a server-client connection, how do i make it UDP?

 

[DJ-CHRIS1]

lets say taht im making a server-client connection, how do i make it UDP?

Manage to get the soruce code (For many products, this will involve breaking into a building and finding it). The second step is to completly redesign the program. The third step is to recompile and run it.


Basicly, the program chooses what it wants to do. 99% of the software out their does not let you choose between UDP and TCP

 

[bilbus]

in other words you can not.

why do you want udp?

 

[systeq]

in other words you can not.

why do you want udp?

i smell a jr peewee league jax0r in the making...errr, dreaming

 

[Dnsgm]

it's for a coming up game that we're developping. We've used only TCP so far, but the game is starting to lag. So i did a research on it and it said UDP is better for games. But how do we choose to UDP instead?

 

[UK31337]

UDP is "stateless" - it just blasts away packets and hopes for the best. As there's no error checking at either end, it's faster - but you get "lag" because some packets are missing/corrupted, hence why your CS man leaps from one side of the screen to the other... it's because the packets for the motion in between are missing, or arriving too infrequently to be any use, by which time the game might "guess" where they moved to.

TCP, on the other hand, has acknowledgement on packet receipt, and calls for a resend if there are any packets missing. This creates overheads, and doesn't make any sense seeing as the packets, under TCP, have to be scheduled into the correct order.

UDP is better, seeing as it's a whole damn lot faster, which is especially important if you're playing something like UT. TCP creates too many overheads, and the 2-way communication slows everything right down.

Use UDP.

 

[systeq]

UDP is "stateless" - it just blasts away packets and hopes for the best. As there's no error checking at either end, it's faster - but you get "lag" because some packets are missing/corrupted, hence why your CS man leaps from one side of the screen to the other... it's because the packets for the motion in between are missing, or arriving too infrequently to be any use, by which time the game might "guess" where they moved to.

TCP, on the other hand, has acknowledgement on packet receipt, and calls for a resend if there are any packets missing. This creates overheads, and doesn't make any sense seeing as the packets, under TCP, have to be scheduled into the correct order.

UDP is better, seeing as it's a whole damn lot faster, which is especially important if you're playing something like UT. TCP creates too many overheads, and the 2-way communication slows everything right down.

Use UDP.

thanks for the quick textbook reading, but he wants to know HOW to enable UDP usage...i think you should ask this question in "computer programming" not here....