Re: ETHERNET TCP Connections
Hi,
Its better to keep the TCP connection alive, its also much faster since a new connection made cost time and since it does not cost any thing to keep it open ist much better.
TCP can be seen as a error free data pipe, if you put packets of data in to it you will get them out on the other side of the link error free... your packets can be broken into smaller chunks and your software should be able to take care of this, you can since all chunks always will arrive in the correct order.
If your application can suffer from data loss you can also use UDP, advantage is that you don't need to make or brake a link but arrival and order are not always 100% what you expect
.. if your application is only over a small network (Ethernet) than you can expect 100% of the UDP to be delivered correctly.
If you are pushing that TCP over ethernet the MTU (Max Transmission Unit) before they are broken into chunks by TCP is about 1500 bytes..
You can also find out the MTU of your network before you start transmitting packets to be 100% sure they are not broken, but better is to write your code so it can handle these events..
good luck,
Paul.