You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some radio stations have more than one channel. At the moment, each time a user switches between channels, a new sessionID is assigned to him/her. When switching back to the station they previously listened to, they will also receive a new sessionID as they are currently not stored.
I'm wondering what would be the best way to improve this situation. We could:
Store the last sessionId for each channel on the client
Reuse the same sessionId for multiple channels (server side management)
keep everything as it is.
The text was updated successfully, but these errors were encountered:
Don't forget to be careful: In case the session became invalid, a new session has to be created. That means channel switching should rely on the same mechanisms as normal channel startup.
Some radio stations have more than one channel. At the moment, each time a user switches between channels, a new sessionID is assigned to him/her. When switching back to the station they previously listened to, they will also receive a new sessionID as they are currently not stored.
I'm wondering what would be the best way to improve this situation. We could:
The text was updated successfully, but these errors were encountered: