Websocket connection and reconnection

backend-heavy.mermaid

🌟-client-heavy.mermaid

Backend-heavy Pros:

• Minimizes work/ requests by user and keeps more transactions within the cloud
• Allows the client to have their token refreshed without coupling that act with reconnecting to the backend???
  • (so they don't reconnect unless they come back to their machine)

🌟 Client-heavy Pros:

• Eliminates the need for defining a "reconnect" message (since our reconnect message can simply be GCP terminating the connection)
• Eliminates the need to schedule the reconnect request every 5 minutes since we can rely on GCP just terminating the connection
• Allows client to reconnect seamlessly during redeploy

Home-rolled Session Token Pros:

• Eliminates the need to interact with OAuth providers (for as long as they keep their browser open so the OAuth partner isn't needed for image lookups... I should re-write that....)
• Allows us to decide the durations and limitations of their session... just check when the session was created and if it's expired, delete it from the db if it's no good.