Skip to content

Namespace

Michael Palumbo edited this page Jun 22, 2020 · 17 revisions

document all address patterns for messaging across the mischmasch/teaparty system. Under "messages", list the 'cmd', what it's for, source and destination, etc.

Currently we have 4 websockets running (names relative to app.js): teapartyWebsocket deltaWebsocket localWebsocket p2pWebsocket

teapartyWebsocket

  • port 8090
  • connect to teaparty on startup. receives updated list of pals, host, and host ip.
  • if first to connect, app.js is assigned host.

Messages

newClient Sent from app.js to teaparty.

{ 
  "username": "machineName",
  "ip": "publicIPAddress", 
  "vr": 0,
  "sound": 1,
  "spectator": 0
}

guestlist sent from teaparty to all app.js instances

{
  "pals": {
    "michaelpalumbo": {
      "username": "michaelpalumbo",
      "ip": "...omitted...",
      "vr": 1,
      "sound": 1,
      "spectator": 0
    }
  },
  "headcount": 1,
  "host": "michaelpalumbo"
}

deltaWebsocket

  • port 8081
  • runs either as host or pal (determined by teaparty)
  • handles the got

Messages

localWebsocket

  • port 8080
  • communicates with other local clients (i.e. VR, max client)

Messages

p2pWebsocket

(possibly not a websocket, also not yet a priority) p2p communication of non-edit data, i.e. controller/hmd data, across global system.

Clone this wiki locally