In our internal application, we utilize Indicium Universal's resource/task staging functionality for executing tasks and updating forms with layouts and default values. However, a developer questioned what would happen when a resource or task is staged and then left idle.
Say a client is improperly closed or disconnected (the active Universal GUI tab is closed, connection is lost, a power outage, etc.) just after they staged a resource. Indicium Universal has no way of knowing what to do with the staged resource, at least not through client instruction.
Is there some default configuration for cleaning up memory taken up by idle staged resources? Is that something individual implementations should configure?
If not, I would say a good default expiry time is equal to the lifetime of the user’s session. That way, when a user's session is expired, all their staged resources are cleared from Indicium Universal's memory.
Best answer by Vincent Doppenberg
View original