I've been only supporting a TCP socket connection to my server, but now I'd like to add UDP to my architecture. I'd like to use TCP for mission-critical packets, such as when a team scores a point, some one drops in or out of a game, etc, and UDP for things like updating player states. Would this be a good idea? I read on a blog that it's best to use UDP for everything, and try to emulate TCP for those important messages. It stated that having TCP in use would bog my network connection down... This is interesting since I'm sure any device that has Internet connectivity nowadays, whether it's a computer, tablet, or smartphone, it's probably always online transmitting data for an app.
I mean, there's up to 65536 theoretical ports you can which means some one didn't think 255 connections weren't enough back when these protocols were being designed. I've been told that the first 1023 are off-limits because many OSs uses those to provide standard services like mail, FTP, etc. So, that would make sense to me.