[ 
https://issues.apache.org/jira/browse/WICKET-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260340#comment-13260340
 ] 

Martin Grigorov commented on WICKET-4444:
-----------------------------------------

Hi Don,

As you can see from my earlier comment I did a poll about this feature and 
there were no many interested people.

Why do you call it a "fix" ? It is actually a new feature.
What kind of problems do you experience at the moment ? 
Please describe your use case in the users@ mailing list.
                
> Add a callback to the Session which is called when the HttpSession is 
> invalidated
> ---------------------------------------------------------------------------------
>
>                 Key: WICKET-4444
>                 URL: https://issues.apache.org/jira/browse/WICKET-4444
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.0.0-beta1
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>         Attachments: WICKET-4444.patch
>
>
> Currently the only notification that a user session has gone is 
> org.apache.wicket.Application#sessionUnbound(String) which gives only the 
> http session id as context.
> With the proposed change it will be possible to have an explicit callback 
> method in o.a.w.Session itself. It will be called after explicit usage of 
> Session#invalidate(Now)() or http session expiration due to inactivity.
> See the proposed patch.
> One "problem" is that now the http session attribute that holds the instance 
> of SessionBindingListener will keep a reference to the Wicket session, but I 
> think this should not cause bigger memory footprint because the same Session 
> instance is already kept in another attribute in the http session, so the 
> serialization process will just link the second to the first. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to