Hi.
I'm only just starting to look at this project but I find the architecture of backed vs. frontend vs. browser interesting.
It seems that the host that I want to do the saving/loading needs to run both the client and a web-browser to connect to the client. Am I understanding correctly so far?
I wonder why the client (in the general sense of a client, not your implementation of a client) cannot simply be the browser and what you call the client (the part that presents the HTTP UI to the web browser) be part of the backend.
In such an architecture, the web browser loads and saves files through it's native ability to read and write files from/to local files and communicates these between itself and what you are calling the client.
Ultimately a client host only needs a browser and not the client application.
Hi.
I'm only just starting to look at this project but I find the architecture of backed vs. frontend vs. browser interesting.
It seems that the host that I want to do the saving/loading needs to run both the client and a web-browser to connect to the client. Am I understanding correctly so far?
I wonder why the client (in the general sense of a client, not your implementation of a client) cannot simply be the browser and what you call the client (the part that presents the HTTP UI to the web browser) be part of the backend.
In such an architecture, the web browser loads and saves files through it's native ability to read and write files from/to local files and communicates these between itself and what you are calling the client.
Ultimately a client host only needs a browser and not the client application.