Implement WebSocket's in to API

[martiangirlie]

• New API will be an event-driven architecture using socket.io
• If it's possible to not absolutely destroy the mobile's compatibility with the old API before switching over, that'd be great.
• Follow this documentation for structuring the api: reference
• Registered sockets will include:
  • connection: establishes initial connection, registers each socket connection. reference1, reference2 reference3
  • getPins: sends most recent version of pins to client
  • updatePin: updates a pin (should emit requestPin)
  • addPin: adds a new pin (should emit requestPin)
  • sendNotification?

[martiangirlie]

• How will sending a refreshed list of pins out to each client on each pin addition work when scaled for high traffic?

[martiangirlie]

We'll do the restructuring of the API in a separate ticket, don't want to overload this one.

[martiangirlie]

https://tutorialedge.net/typescript/typescript-socket-io-tutorial/

[martiangirlie]

https://medium.com/@willrigsbee/how-to-keep-track-of-clients-with-websockets-1a018c23bbfc

[martiangirlie]

maybe ijplement something more akin to "views" so things like "counts" for visualizations come in.

[martiangirlie]

Group protest users within. the same socket group https://stackoverflow.com/questions/51266723/creating-a-private-room-through-a-link-using-node-js