Transfer Images via Backend Instead of RPCs

[tinxx]

The Backend provides an API for sharing Code City projects with its clients. The Code Cities are static data that cannot be modified by SEE clients.

Similarly, API endpoints should be implemented to allow uploading dynamic data by SEE clients.

• Endpoint to upload files for a server by SEE clients, authorized by the server password
• Endpoint to retrieve these files via their id, authorized by the server password

---

The first use case that should be implemented along with the API is as follows:

• Replace the transfer of images used in drawables (whiteboad) to use the back-end API instead of the standard RPC method.
  • The SEE client uploads the image to the Backend via the new API endpoint.
  • The SEE client receives the FileData metadata object as a response from the Backend.
  • The SEE client constructs the URL with the file id to retrieve it via the second endpoint
  • The URL is stored in a DataPath and transferred via the RPC mechanism to the other clients.
  • Optionally, the old method of transferring images via RPCs can be kept as a fallback for cases when no backend server is configured (e.g, in the Unit editor).