Task #9168 (new)
Opened 12 years ago
Last modified 8 years ago
RFE: permit immediate detachOnDestroy setting. — at Version 1
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | OMERO-Beta4.4 |
Component: | API | Version: | n.a. |
Keywords: | n.a. | Cc: | cxallan, cneves, jburel, wmoore |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description (last modified by jmoore)
See #8812
A race condition exists between the time when createSession() has been successfully called and detachOnDestroy() can be called on the returned object. If anything happens in that period (network issue, out of memory, out of file handles, etc), then when the session is closed by glacier (usually 10) minutes later, the session may be closed completely.
Clients should be able to pass {"omero.detach_on_destroy":"true"} (or similar) during the call to createSession, joinSession, and createClient in order to set the flag server-side immediately. Helper method and/or optional arguments in each SDK should make this easy to implement. E.g.
def createSession(self, username, password, detach=False):