Skip to content

Resolve "Get Jitsi connection working"

Chris Lemaire requested to merge 52-get-jitsi-connection-working into development

The following setup facilitates the following workflow: patient tablet gets setup with a calendar with special URLs.

Each URL is a /connect/patient/{UUID} URL that represents a ClaimedTimeSlot and the action of creating it. This link should never be shared with anyone outside the tablet. When clicking the URL, the name and password for a room get generated on the server and the patient tablet receives them first. The patient tablet then initializes the room with that name and password.

The guest URL is simply /connect/guest. This is the waiting room where guests will see their upcoming time slot and possibly some information about what to do/not to do/calming texts. Once the patient room is initialized, the waiting room is removed and replaced by an embedded Jitsi call. To see if the Jitsi call is ready, the guest.html page contains code to poll the server for a room.

  • Add Javascript functions for setting up the guest-side connection and for setting up the call on the patient-side.

  • Add ConnectionController implementation of the patient and guest functions.

  • Add initial upcoming timeslot representatives in guest.html.

  • Add exceptions representing certain events in the server side.

  • Add DatabaseLoader entries for time slots for testing.

  • Annotate OneToMany fields that are mapped by another entity with @ToString.Exclude to make sure debugging statements make sense.

Closes #52 (closed)

Merge request reports