Jul 26, 2019
Hi Everybody, this semester i will be teaching a Game Networking course for my university and im struggling to choose the proper technology and topics to teach due to the UNET deprecation.
For one side i have the new Transport API that as far as i know in the recent updates support differents QoS trough Pipelines, but the API is still in experimental phase, so im not sure about his stability. On the other side i have LLAPI that is very similar to the new Transport Layer but is gonna be deprecated. Finally i have HLAPI that is more simple but gonna be deprecated also but will not have anything similar to replace it.
In previous instances of the course i have used HLAPI for its simplicity, but now im pretty sure i will be using LLAPI to prevent my students to be overwhelmed by all the boilerplate code and new structures they have to use in the new Transport Layer (Native Lists, etc) and at the same time preparing them to easely migrate to it and understand the tools that will be built over it (like the FPS Sample). My idea is that they build their own game protocol over LLAPI, and mix it with HTTP services to persistence like the following link specifies:
What do you think? Greetings!