The performance hit is not as that severe. You must also consider the reliability of the connection. With TCP connections you get error correction and automatic retries. With UDP, you get none of that. It is a send and hope method.
Make sure you evaluate more than the just the performance cost of creating the listening socket.
I have written many client/server applications and have found that the TCP method of implementation seems to be the best. The main reason for UDP would be transmission of data that is not neccesarily required to be recieved. i.e. the streaming of a movie or sound clip.
Brian Seekford
Brian Seekford
Seekford Solutions, Inc.http://www.SeekfordSolutions.comInternet ActiveX Controls and .NET Class Libraries.
SMTP/S FTP POP3/S HTTP/S SNTP MIME PING WHOIS TRACEROUTE NNTP DNS MX
Base64, UUEncode, yEnc, MD5, SHA1, URL, Quoted-Printable.
Resizer and Tooltips
Email Verification and more. Check us out!