Chris Harrison Stacey Kuznetsov Mariya Lysenkova Jennifer Refat Gabriel Sinkin

MMORPG Massively Multiplayer Online Role Playing Game Wide target audience Hundreds/Thousands of players Large, persistent world Movement, Chat, Trade, Combat

Protocol Plain text (abstracted) Simple and extensible Command composition –Leading character determines command type –Server and client know command structure –“M ” –Movement; Player 45 moving from x=1356, y=2483 to x=1401, y=2237.

Command Flow Chart

Server Architecture Network Communication –BSD Sockets –One socket per client, two-way data flow –TCP (not UDP) Server broadcasts commands once (no streaming data) Data less time-sensitive than other applications –TCP Header: 20 bytes. Movement Command: ~25 bytes. ~50 bytes per command Clients generate a command every ~2 seconds 1000 concurrent clients ~25Kbps upstream data Naïve Broadcasting: 25Mbps!

Server Architecture Handle many concurrent clients –Posix Threads –Main Accept thread Waits for new client connection Spawns new client handler thread –Thread for each client Receives command string Adds command to command queue Sleeps –Broadcast (responder) thread Continuously processing commands unless queue is empty Selectively broadcasts to relevant clients –Movement, chat, combat to local area –Private chat, trade, to single player –Taps into player-data-storage class (updating and getting information)

Server Architecture

Life of a Command

Mock Screenshot