Consider websockets for pushing results

[robertutterback]

In previous prototypes I used websockets to push results as they were reading, which I still think is the right approach. This way we don't overload the server and many viewers can easily subscribe to get the results of any given analysis.

However, Sveltekit doesn't easily support websockets. I think it can be made to work (search for relevant issues in the sveltejs/kit repo, although getting it to work both in dev and adapter-node is a pain. I think they are working on it, but given their insistence of providing first-class support serverless adapters, it may be a while. (Someone should fork Sveltekit and just focus on node adapters to make faster progress...)

So my choices are:

1. Just do polling (which I am doing now)
2. Wait until Sveltekit provides better support
3. Switch to plain Svelte with my own setup, probably express or polka.

I'm not even experienced enough to know where Sveltekit holds me back, so there are probably other benefits to (2). Especially since I do not care much about the SSR features of Sveltekit.

[robertutterback]

Actually, I missed perhaps the best solution: make the websockets server separate from sveltekit. It doesn't need to be related, anyway. The only thing in common is authentication, which will be working with Redis/Mongo anyway.

Just set up a separate websockets server (could even be Python). The server just needs to accept connections, validate them, and send results as they are available.