Task #5887 (new)
Opened 13 years ago
Last modified 9 years ago
LIM: possible to logout from web with background activities
| Reported by: | jamoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | ux@…, web-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Though in the case it's probably not too important, as we add more background activities (scripts, etc) allowing the user to logout (and therefore not have access to the proxies) may be dangerous. Perhaps there should be a pop-up to prevent logout? Another possibility would be to allow finding all running handles (scripts, delete, etc).
Change History (19)
comment:1 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.3 to OMERO-Beta4.3.1
comment:2 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.3.1 to Unscheduled
comment:3 Changed 13 years ago by jmoore
- Priority changed from minor to critical
comment:4 Changed 13 years ago by jburel
- Milestone changed from Unscheduled to Usability Backlog
comment:5 Changed 12 years ago by jmoore
- Cc web-team@… added
- Owner changed from atarkowska to cxallan
Something else that may have been handled by the current rework. Anyone?
comment:6 Changed 12 years ago by wmoore
Not handled currently. We could do the check client-side, but as with all these things (as we've been discussing) it would be nice if the server kept track of current jobs, AND a history of jobs. E.g. start a script running from my Matlab client - then go to Insight and pick up the result. OR "run the script that I ran 10 mins ago, loading all the same parameters by default"
comment:7 follow-up: ↓ 8 Changed 12 years ago by jmoore
Though I could certainly imagine having more (is there a story?), is this not in the first instance the same as getStatefulServices to see what's running, i.e. what would prevent changeActiveGroup?
comment:8 in reply to: ↑ 7 Changed 12 years ago by cxallan
Replying to jmoore:
Though I could certainly imagine having more (is there a story?), is this not in the first instance the same as getStatefulServices to see what's running, i.e. what would prevent changeActiveGroup?
To a certain extent it is but the issue really is universal and it applies to all our clients. Can you really prevent someone from logging out just because they have a delete or script currently running? Does that even make sense from a UI perspective? I doubt it. A warning? Maybe. So without some form of persistent, cross session store that the server can provide to clients I'm not sure we can solve the problem effectively.
comment:9 follow-up: ↓ 10 Changed 12 years ago by jmoore
Understood. If it's best to leave this until we have such infrastructure, that's fine. Guess I'm mostly worried about the error-handling of those processes if the user logs out. (We should also check that once they've logged out that the session doesn't get pulled out from under the processes)
comment:10 in reply to: ↑ 9 Changed 12 years ago by cxallan
Replying to jmoore:
Understood. If it's best to leave this until we have such infrastructure, that's fine. Guess I'm mostly worried about the error-handling of those processes if the user logs out. (We should also check that once they've logged out that the session doesn't get pulled out from under the processes)
Agreed. OMERO.insight also just only gives you the standard "Are you sure you want to quit?" dialog so we should evaluate this in the context of both clients.
comment:11 Changed 10 years ago by jamoore
- Cc ux@… added; saloynton jburel removed
- Milestone changed from Usability Backlog to 5.1.0-m1
- Version set to 5.0.2
See also https://www.openmicroscopy.org/community/viewtopic.php?f=6&t=7544&p=14162#p14162
Has there been any other recordings of this issue?
comment:12 Changed 10 years ago by jamoore
- Owner cxallan deleted
Taking Chris' name off of this. Not sure of the current status.
comment:13 Changed 10 years ago by jburel
- Milestone changed from 5.1.0-m1 to 5.1.0-m2
Sorry this got missed. Added to a trello card so we do not forget again.
comment:14 Changed 9 years ago by jamoore
- Milestone changed from 5.1.0-m2 to 5.1.0-m3
Pushing again. If there could be a comment on the priority/feasibility of this, I'd appreciate it. If it's not being done for 5.1, where are we pushing it to?
comment:15 Changed 9 years ago by wmoore
- Owner set to wmoore
It should be relatively straight-forward to check if there are any "Activities" in the "running" state and if so, give an option to Cancel the Logout.
comment:16 Changed 9 years ago by jburel
Did you check that one Will?
comment:17 Changed 9 years ago by wmoore
I looked at it but haven't started anything. It just depends on the priority. I didn't really think it was "critical", but happy to tackle it anyway.
comment:18 Changed 9 years ago by wmoore
- Milestone changed from 5.1.0 to 5.1.1
- Priority changed from critical to major
Needs some more discussion about what we need right now, vv future.
Not critical (yet) and not for 5.1
comment:19 Changed 9 years ago by wmoore
- Milestone changed from 5.1.1 to Unscheduled
- Version 5.0.2 deleted
Increasing prioritization so that we review. If we add more background tasks (or anything with ConcurrencyExceptions) then we'll want to be able to warn or re-attach to these services.