SoylentNews is people
SoylentNews
An introduction to networking for game programmers:
Hi, I'm Glenn Fiedler and welcome to the first article in my article series Networking for Game Programmers
In this article we start with the most basic aspect of network programming, sending and receiving data over the network. This is just the beginning – the simplest and most basic part of what network programmers do, but still it is quite intricate and non-obvious as to what the best course of action is. Take care because if you get this part wrong it will have terrible effects on your multiplayer game!
You have most likely heard of sockets, and are probably aware that there are two main types: TCP and UDP. When writing a network game, we first need to choose what type of socket to use. Do we use TCP sockets, UDP sockets or a mixture of both?
The choice you make depends entirely on what sort of game you want to network. So from this point on, and for the rest of this article series, I'm going to assume you want to network an action game. You know games like Halo, Battlefield 1942, Quake, Unreal, CounterStrke, Team Fortress and so on.
(Score: 3, Informative) by VLM on Monday January 02 2017, @10:54PM
Ironically the "legacy" pre-PS/2 and PS/2 hardware keyboard interface are synchronous bidirectional serial and USB is error correcting also. Also SSH is how I connect over TCP to most all consoles now a days.
A good example along your lines of UDP for UIs "send it and hope it arrives" is some of the mostly-write-only video card hardware interfaces over the past couple decades. Like before PCI, the "special" stuff like AGP and weirder. Those truly were some write only, hope it gets there, protocols.