My Shopping Cart

[ 0 ]

View Cart | Checkout

Game Developer Research
bullet Research Reports

bullet Contractor Listings

GDC Vault
bullet Individual Subscription

GDC Audio Recordings
bullet App Developers Conference 2013
bullet GDC Next 2013
bullet GDC Europe 2013
bullet GDC 2013
bullet GDC Online 2012
bullet GDC Europe 2012
bullet GDC 2012
bullet GDC 2011
bullet GDC 10
bullet GDC 09
bullet GDC Austin 08
bullet GDC Mobile 08
bullet GDC 08
bullet GDC Austin 07
bullet GDC Mobile 07
bullet GDC 07
bullet GDC 06
bullet GDC 05
bullet GDC 04
bullet GDC 03
bullet GDC 01
bullet GDC 2000 & Before

Newest Item(s)

Why Now Is the Best Time Ever to Be a Game Developer

Ingress: Design Principles Behind Google's Massively Multiplayer Geo Game

Playing with 'Game'

Gathering Your Party with Project Eternity (GDC Next 10)

D4: Dawn of the Dreaming Director's Drama (GDC Next 10)

Using Plot Devices to Create Gameplay in Storyteller (GDC Next 10)

How I Learned to Stop Worrying and Love Making CounterSpy (GDC Next 10)

Luck and Skill in Games

Minimalist Game Design for Mobile Devices

Broken Age: Rethinking a Classic Genre for the Modern Era (GDC Next 10)

Storefront > GDC Vault Store - Audio Recordings > More GDC > GDC 2005

View larger image


A Case for Message Passing Architectures
Price $5.95
Stock Unlimited
Weight 0 lb, 0 oz
SKU GDC-05-138
A Case for Message Passing Architectures,

Programming, Lecture

Dave Weinstein
Security Development Engineer, Microsoft
Message Passing Architectures have been used in game development for at least a decade. With the ever increasing size of development teams, and the increased prevalence of multiplayer game support, how do the advantages a well designed messaging system offers for code coherence and intelligibility and multiplayer implementations stack up? What mistakes in a message passing system can remove these advantages, and how can they be recognized and avoided?

An overview of three message passing architectures used in shipped games, with examples of strengths and weaknesses. Examples of how the use of a message passing architecture can allow for clean abstraction layers, and minimize cases where different engineers working on different components fall into each others critical paths. A model for how message passing architectures can keep the single player, client, and server code paths almost identical, minimizing code rot and cases where new features in one area break other modes. Problem areas, weaknesses, and potential implementation and team and project management issues for message passing architectures.

Please leave this field blank.

There are no related products to display.

Related Products...

Please leave this field blank.