Dao transport branch

[donny138]

This PR contains two things:

• DaoGameFlow.txt
  • This file outlines the rough behavior / interaction of the client and server dao programs
  • This is mostly here for brainstorming, may need to be changed or modifed
• DaoMsgDef.py
  • This file implements a rough outline for a communication protocol. See more below
  • This file implements the tasks for DaoGame #10
  • There is some temporary code within this file that will need revision / removal before full implementation is ready

Note: This PR does not add anything involving exchanging data using sockets. Just the definitions and objects related to different types of messages these programs may need to exchange in the future.

The following stuff now exists in the Dao message stuffs!

• Message codes for different messages

  • These have rough payloads associated with them

• A Standard Dao Message object

  • stores everything associated with messages to exchange
  • can be created from just a series of bytes (what sockets actually exchange info using)

• Message constructors

  • creates a Standard Dao Message for a particular message code
  • takes any payload data for it's message code as input and adds it as bytes to the message object

• Message extractors

  • extracts payload data from a Standard Dao Message into normal variables types

• TEMPORARY MAIN FUNC:

  • This will be removed at some point
  • Contains a bunch of test / example code using everything above

[donny138]

@milkshake-moo There isn't any actual communication yet! Think of the message stuff as the words the future programs will use to communicate!

The next step ( #11 ) is to write some scripts that can use these words to talk to each other.

[milkshake-moo]

@donny138 That's what I figured. Having all of the communication "types" and messages defined here will make the actual implementation easy, I think/hope!