alexbudarov
commented
3 years ago Relates to Haulmont/jmix-audit#12
Open alexbudarov opened 3 years ago
alexbudarov
commented
3 years ago Relates to Haulmont/jmix-audit#12
Current "user sessions" implementation doesn't provide the same amount of functionality like CUBA had.
In CUBA you could read attributes of other sessions. Example use cases:
mark each session from web service or webdav with special flag, so you can limit number of web client simultaneous connections but not limit webdav sessions (https://www.cuba-platform.ru/discuss/t/kak-otlichit-sluzhebnye-sessii-webdav-ot-shtatnoj-sessii-polzovatelya-v-prilozhenii/5068)
"Telephony" use case. Each user session has attribute "extension number". When current application receives web service call from cloud telephony - this call contains extension number. We need to loop through all active sessions, find which user session corresponds to the extension number and immediately initiate UI refresh to show incoming call to the user.
In Jmix currently you only can read current user session's attributes (with SessionData bean, takes them directly from HttpSession). The UserSessions bean provides list of all sessions but only with limited amount of parameters, no access to attributes.