More ignorance I suppose but that reads like the session state isn’t maintained on the server after all. Instead the client actually “remembers” the state, sends it back to whatever server answers the call who then reconstructs the session state from what was sent. After spending so much time debating how to control and optimise how much session memory to use server side I’d feel a right arse if the above as to be true meaning the server doesn’t keep session state at all.
Alternatively I am failing to distinguish accurately between the web socket mechanism and the session, in which I am still in the same dark about how the code handling the events pushed on the web socket ends up having access to the session data.
Or I am mistaken about assigns being part of session memory?
Thanks, for helping out. It must seem like trivial a d/or overthinking but I have a lot riding on layers of software built on a possible misconception.
