Open TheGrandmother opened 8 years ago
how about using sessions in the browser?
I'm considering closing this. Since the server still logs out upon connection termination.
I have added a warning when the user tries to leave the page.
This could actually be solved quite easily.
Just let te client send a REESTABLISH
message with the session ID upon every new connection. We then have the server store valid session ID's and if such a session ID exists the connection is immediately reestablished.
If the session id is not valid on the server (due to a logout or a time out) the server will await a normal authentication.
Well this is tied in and in a bit of a conflict with issue #26.
We need to have a way of making the connections persistent when one reloads the web page. Unfortunately that is not possible to do with javascript.
We some how need to add a connection id so that the the server can detect when the same client gets a and remove the old one.
This should happen seamless. This might be hard to implement but in the meantime I could add a warning pop-up when someone tries to leave or reload the page.