1回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
AppStream sessions are not re-used or forcibly taken over should a user log in a second time. A new session is established on a new instance and old session still remains, as you indicated.
For a user to change devices/browsers/locations and retain the current session, they would need to disconnect first and reconnect within the specified timeout period (admin-configurable) to connect to the same session and continue, you can also try to expire a session using AWS CLI command: expire-session to expire a previous session.
回答済み 6ヶ月前
Yea the expire-session command is a bit to heavyweight as it destroys the instance. I might look into seeing if I can have my app call DCV to disconnect the other connection although the sequence of events won't be ideal there. I'll have to have some sort of service though as DCV commands need admin privileges.
Well I implemented this so that
dcv close-connectiongets called prior to handing out a new createStreamingUrl but unfortunately the existing client immediately tries to reconnect and succeeds.We were able to use the disconnect event to disable the auto-reconnect. We coupled this with a service do this selectively and only allow the most recent connection to reconnect.