[
https://issues.apache.org/struts/browse/SHALE-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41372
]
Alexandre C. Barbosa commented on SHALE-453:
--------------------------------------------
As stated in the conversations from the related threads, I don't think that the
scenario b) will be an advantage (because of the multiple dialogs open
simultaneously). But I think that the scenario a) will be a great improvement
to the dialogManager. But how this would work in the case of opening links into
a new tab / window? Is it possible to shale to know if the request will be
opened into the same or different tab/window?
> Shale Dialog uncovered usescases -> probable memory leak due to them
> --------------------------------------------------------------------
>
> Key: SHALE-453
> URL: https://issues.apache.org/struts/browse/SHALE-453
> Project: Shale
> Issue Type: Improvement
> Components: Dialog
> Environment: All Versions
> Reporter: Werner Punz
>
> After digging through the codebase, I could not find any timeout code for
> shale dialog, after a discussion on the mainlinglist
> it does not seem to be there, dialogs if not properly terminated stay there
> until the session times out.
> Following usecase:
> User is in the middle of a dialog and alters the url manually, the dialog
> stays in ram until the session times out.
> Following solutions szenarios could work:
> a) Be able to set wildcards to cover all non dialog urls so that the dialog
> is terminated properly
> b) Give it a timeout garbage collecting thread probably with a possible ajax
> callback to keep the page refreshed, in multi window or long running window
> szenarios.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
