On.Programming

For most of us, programming (or more generally – software development) is all the life is about.

IT Hares are not different. And they have more than just quite a few bits to share about programming…

Part IIIa: Server-Side (Store-Process-and-Forward Architecture) of 64 Network DO's and DON'Ts for Game Engines

June 8, 2015 by “No Bugs” Bunny

Incoming queue: cake. Processing: restaurant table. Outgoing queue: WC.

Abstract:

A Panegyric to Store-Process-and-Forward architecture

Quote:

"With proper logging, in most cases a bug can be found from one single crash/malfunction.

Filed under: On.System ArchitectureDistributed systems(Re)ActorsOn.ProgrammingNetwork Programming

Read more

Part IIb: Protocols and APIs (continued) of 64 Network DO’s and DON’Ts for Game Engine Developers

June 1, 2015 by “No Bugs” Bunny

In response to your SYN packet as referenced above, we're pleased to inform you that...

Quote:

You shouldn't count on outsmarting all those millions of highly motivated hackers operating in an environment under their own control.

Another Quote:

Burst consisting of several million packets, may start causing observable issues for a mid-size ISP.

Filed under: On.System ArchitectureDistributed systemsOn.ProgrammingNetwork Programming

Read more

Part IIa: Protocols and APIs of 64 Network DO’s and DON’Ts for Game Engine Developers

May 25, 2015 by “No Bugs” Bunny

Protocols: Alice talks to Bob

Quote:

While using framework is fine, forgetting about it is not.

Another Quote:

Even if you're forcing the auto-update every time the game app starts, there still are users who were online at the moment of the update, and those who found a way to bypass game updates

Filed under: On.System ArchitectureDistributed systemsOn.ProgrammingNetwork Programming

Read more

Part I: Client Side of 64 Network DO's and DON'Ts for Game Engine Developers

May 18, 2015 by “No Bugs” Bunny

Caught in the NET

Abstract:

Network support is not so trivial as it looks. Client side has quite a few things to screw up.

Quote:

We’re treating our readers as intelligent beings who can use Google and/or StackOverflow

Filed under: On.System ArchitectureDistributed systems(Re)ActorsOn.ProgrammingNetwork Programming

Read more