| 114 | === Communicating with the party through the websocket |
| 115 | As mentioned, the /run command returns a websocket address through which communication with the running party instance takes place. |
| 116 | |
| 117 | The connection thus created allows Inform JSON objects to be sent to the party, and Action JSON objects to be sent by the party. The protocol determines the meaning and order of these. |
| 118 | |
| 119 | If the party throws an exception, this exception should cause the socket to close (as a party can only do Actions). A close reason can only have a 123 character explanation which generally is too short for stacktraces. It is recommended therefore that such explanation is a reasonably human readable abstract of the full cause. The full stacktrace can be shown/logged in full detail on the partyserver. |
| 120 | |