Skip to content

Conversation

@mickmister
Copy link
Member

No description provided.

@mickmister
Copy link
Member Author

I think it would be beneficial to introduce a hand-held user id system. The client receives two tokens on first connect. One to put in localStorage, and one to put in sessionStorage. One is user id and the other is connection id. These are JWTs with the public ids in them.

Then the client can connect its websocket, and provide these values as query params. Second browser tab will have an existing user token, but needs a fresh connection token. We can provide the user/connection id info to any user-land created action. Also rpc middleware should be able to decorate this same userData coming through easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants