Nexus-Like Integration Architecture

• Coordinating service
  • Where does this live?
    • Local network (wifi, ethernet)
    • Physically close (Bluetooth)
    • Remote server "in the cloud"
  • How do coding environment instances connect?
    • See above
  • Could a coding environment instance act as a local coordinating service?
    • Will need some mechanism by which other instances could connect
• Coding environment instances connect to the coordinating service

Admin Interface for a Coordinating Service in the Cloud

• Begin new shared activity
  • User selects from configured/built shared activities
    • For example, splatter painting
  • System generates a short random password
• Will need some notation for making shared activities
  • Similar in scope to Nexus configurations but with perhaps more C2LC-specific supports, such as coding environment "roles"
    • A coding environment connecting to a shared activity may query the roles supported by the activity and then select a role to play

Coding Environment

• Click button "Join Shared Activity"
• Environment prompts for password
• After successful password entry, the user is presented with a selection of roles available for the activity
  • For the splatter painting example, we might have:
    • Shared display (shared output only for rendering the art)
    • Student interface (for sending instructions to add to the art)
• After role selection, the coding environment interface is configured appropriately