[Major] Refactor the server to a REST api which saves "post" data into buckets and re-loads the same data with "get"

[dbirman]

We'll just use JSON queries to represent all the data. To prevent resources from getting overwhelmingly large we'll host the binary blob data separately (as .bytes files) and just reference these from JSON request, so the client then has to download them itself.

Posting data will be restricted by a token, and people will have to pay for their tokens, presumably by some combination of data size and amount of access? For now we'll just leave it unrestricted.

On the Unity side, when you load a bucket it will request the JSON for that bucket and then parse it to reconstruct the scene. One issue is how to "ping" the client to update the scene when the user posts something new to the bucket? Maybe we timestamp the last update and we poll continuously?

[dbirman]

New plan: API talks to proxy, proxy talks to Unity, Unity talks to server. So Unity can independently load a scene from the server, but you can also control the scene from the API. A "Save" message triggers Unity to override what's on the server, and control messages can be used to send back and forth token data and to set the name of the current scene. Seems pretty straightforward?

As far as how data is stored, binary data should probably still be blobbed as bytes files. This should be done on the REST API itself probably so that Unity just sees the standard JSON data itself.