This is a fantastic article - as are most of the technical materials that Tim Sweeney wrote way-back-when. The Unreal system was my first introduction to the architecture of "real" object oriented apps and I refer back to these articles from time to time as a sanity check.
Glad I'm not the only one. I learned to program making Unreal Tournament mods.
The replication model of the Unreal Engine remains one of the best I've ever seen. Nonetheless, as with anything involving a distributed system, it is very easy to make errors.
Even the original UT (version 400) had a serious error due to the ease of marking functions network transportable. The function to cycle maps was marked to allow the client to send it to the server. It was certainly nice having the ability to select maps on any server. :)
His article on the scripting language was also my first realization of the power of DSLs.
I should also say that most of my learning came from studying the header files in the SDK and imagining what the various implementations would look like. The SDK is still available: http://www.udk.com/download
I even taught myself how to write a decompiler so I could see those implementations. This taught me about the PE format, C++ name mangling, and, of course, x86 assembler. Heady stuff for a 20 year-old. :-)
And then this presentation: http://www.cs.princeton.edu/~dpw/popl/06/Tim-POPL.ppt which made me spend months learning what these stupid Monad things are and having to learn Haskell, ML, and Common Lisp in the mean time. (What? C++ isn't the best programming language available?)
While some people learned to program by going to college, I learned by studying _everything_ Tim Sweeney and John Carmack wrote (and practicing, practicing, practicing). Mr. Carmack's release of old id source code is a huge gift to the world.
The Quake 3 network architecture is also a fantastic read.
Anybody wanting to learn how to implement netcode should definitely read them.
The first time I implemented a UDP gameserver, they were invaluable resources for the logic required if you don't already understand how it works. (Selective msgs require acks, most don't, most don't need resends, etc).
By and large, this is still an accurate description of the networking architecture in Unreal Engine today which has been used in such recent games as Gears of War (2005), Gears of War 2 (2007), Borderlands (2009), Medal of Honor (2010), and indeed most Unreal-based games released since '99
While true, I'd say still very relevant. Even though home broadband has improved drastically since 1999, you also have to now consider mobile connections (while high-speed in large cities, they have sketchy service elsewhere, and usually high-latency).
