Initial Proof of Concept

[ajamias]

No description provided.

[tzumainn]

Interesting! Initial question - with only a single websocket port, won't requests from multiple users collide?

[ajamias]

I tested visiting the dashboard from two browsers on the same computer and they were both sending and receiving data on the same websocket port. Some more things I have to do is to are making sure each thread has its own memory scope, make the polling interval configurable, make the client able to connect to the websocket the host is on instead of juts localhost

[tzumainn]

I tested visiting the dashboard from two browsers on the same computer and they were both sending and receiving data on the same websocket port. Some more things I have to do is to are making sure each thread has its own memory scope, make the polling interval configurable, make the client able to connect to the websocket the host is on instead of juts localhost

Were the two browsers two separate users?

[ajamias]

The two browsers were using the same account (uitest). But I am working right now on making each thread have its own thread local storage so that the users will only receive the data that they are meant to receive

[ajamias]

I added SSL to the websocket connection because trying to do this from chrome instead of firefox didn't work without SSL. But I tested this on two different computers and it looks like it works. I didn't test using with two different users because I get a strange 401 error if I try to log into my [email protected] account using openid connect