Improve netlogo command request-response protocol about galapagos HOT 2 CLOSED

Current protocol examples

• Client chat message

{"agentType":"chatter","cmd":"hi"}

• Server chat broadcast

{
  "kind":"chatter",
  "context":"chatter",
  "user":"Bryan",
  "message":"hi",
  "members":["Bryan","BizzleBot"]
}

• Client observer command message

{"agentType":"observer","cmd":"create-turtles 5"}

• Server observer command echo (so the command is displayed in the chat window)

{
  "kind":"command",
  "context":"observer",
  "user":"Bryan",
  "message":"create-turtles 5",
  "members":["Bryan","BizzleBot"]
}

• Server observer command response (not the view update, just the resopnse to the message)

{
  "kind":"response",
  "context":"netlogo",
  "user":"observer",
  "message":"",
  "members":["Bryan","BizzleBot"]
}

• Client observer reporter message

{"agentType":"observer","cmd":"show count turtles"}

• Server observer reporter echo (so the reporter is displayed in the chat window)

{
  "kind":"command",
  "context":"observer",
  "user":"Bryan",
  "message":"show count turtles",
  "members":["Bryan","BizzleBot"]
}

• Server observer reporter response

{
  "kind":"response",
  "context":"netlogo",
  "user":"observer",
  "message":"observer: 5",
  "members":["Bryan","BizzleBot"]
}

Notes:

• "members" is the list of users to display the message to
• In server messages, "kind" will either be the agent type the command or reporter is for, or it will indicate it's a chat message
• "agenttype" serves the same role as "kind" in client messages
• The protocol is very chat oriented right now.

from galapagos.

This issue was moved to NetLogo/Teletortoise#5

from galapagos.