This project is read-only.

Architecture - Client/Server

Server

  • conducts and manages battles in "real-time" or in simulation
  • runs as a service
  • exposes features and functional controls through a REST API
  • battles are described by assembling the necessary objects together via JSON
  • executes battles until battle conditions are met

Client

  • responsible for command and control, and rendering of battles in "real-time" or in simulation
  • sends commands to server
  • receives state from server
  • could be Windows, web, or mobile even

Authentication/Authorization

  • Clients give themselves a user alias and can log into a server+game instance without password (unless the server is at capacity)
  • Have a separate administration interface, web-based? Restrict admins by user+pass in IIS config?

Tech Stack

.NET 4.5 C# for server, whatever for the client

Last edited Jun 13, 2013 at 1:26 AM by Reinderien, version 6

Comments

Reinderien Jun 13, 2013 at 1:23 AM 
What's there so far is sound, but has gaps. I'll add some placeholders.

cokobware Jun 12, 2013 at 4:22 AM 
Any darts at the architecture? Does this seem sensible, or should we consider alternatives?

cokobware Jun 12, 2013 at 4:20 AM 
Since we're wanting to use JSON, and we're using the .NET stack, I suggest we adopt Web API http://www.asp.net/web-api

cokobware Jun 12, 2013 at 4:14 AM 
REST can use JSON or XML...

Reinderien Jun 12, 2013 at 1:31 AM 
Slight formatting; REST is probably the way to go, but JSON is lighter and more easily supported across clients

kasmeltz Jun 11, 2013 at 10:54 PM 
Dat look really good Cory

Should be fun

cokobware Jun 11, 2013 at 10:18 PM 
Looks ok... I think I screwed up and put my thoughts in comments instead of the actual page... fixing...

kasmeltz Jun 11, 2013 at 9:39 PM 
how me edit?