@sova sessions are for maintaining state across requests. If you’re logging in over a websocket, maybe you just store the login details in local state? Alternatively, you could write to the session store manually, if the store doesn’t use cookies. If you are storing the session state in cookies, then you might have to get more creative, e.g. by sending the encrypted data through the socket, and letting js put it into a cookie. Or use XHRs.
thanks weave, yes i came to the conclusion that it is best to store the session stuff locally
@weavejester do you know how I can destructure sente data
that looks like
@sova the same way you destructure any other data, I assume.