Backend integration

[kuhlaid]

After some thought I am treating the server-side, that this front-end connects to, as an API for data pushes and pulls. The reason for this is that I want this front-end app to be not be tied to a specific back-end database or service, and certainly did not want it embedded in this code base. So the front-end UI code is completely separate from the back-end code. This will make it easier for others to work with this code for their own purposes.

The next step will be to create a Svelte component for entering information about the back-end API to connect to (to be saved to local storage). The user will enter/copy the API URL into the front-end which would be saved to local storage, so that will be my next step in this development.

Other thoughts -------------------

Work on server side CSRF token generation from a user authenticated session (this session and CSRF token need to be saved on the server to validate data requests from the client); reference https://portswigger.net/web-security/csrf/tokens.

I really debated if the app needed unique URLs for each component/page (since these could sort of be routed using server requests to specify the component). I felt the Every framework handled this well, but I couldn't justify it in Svelte. Since this will be used as a non-public app, unique URLs do not seem important or useful so I will not bother with routing to more than one URL to deliver content.