[
https://issues.apache.org/jira/browse/WICKET-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900121#comment-15900121
]
Ihor Parashynets commented on WICKET-6334:
------------------------------------------
hello [~mgrigorov]
Thank you for your replay and workaround!
I fully agree about LDM and its thread safety - no further discussion needed.
I think you described it very precisely - this is what I was trying to ask as a
help/clarification at http://markmail.org/message/mq5zs2veaj4q4psg
{quote}
The Session should not be stored on the disk but still I think
#getSizeInBytes() should show the numbers after the end of the request cycle.
{quote}
[~mgrigorov] and I have one more question - If I may... If we need to keep some
information on the session scope level, which is "kind" of {{Model}} (meaning
should be chached/evaluated/detached once per request call) approach - what is
the best technique to do such? As I understood [~soappatrol] keeping
{{Model}}/s in a "_session is dubious at first place_..." but from another hand
reading https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=76385
i can put into the session any object and do clean-up on {{Session#detach()}}
method.
Thank you.
> WicketObjects#sizeof() should detach Sessions
> ---------------------------------------------
>
> Key: WICKET-6334
> URL: https://issues.apache.org/jira/browse/WICKET-6334
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.6.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
>
> Report at users@ : http://markmail.org/message/mq5zs2veaj4q4psg
> Wicket should detach the Session before calculating its size as it does for
> Component and IDetachable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
