[
https://issues.apache.org/jira/browse/OWB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503298#comment-14503298
]
Mark Struberg commented on OWB-1048:
------------------------------------
What do you mean with 'whole map'? We will put the Map<Bean<T>, BeanBag<T>>
into the session. Of course only from the @SessionScoped contextual intances of
this very session. This is _exactly_ the size we had before. Not a single bit
more.
There is also another benefit: We can use a ConcurrentHashMap so this even
nicely works across different threads on the same Server. If a Session gets
written on different servers at the same time then you are in deep troubles
anyway...
> Store @SessionScoped beans in real HttpSession if available
> -----------------------------------------------------------
>
> Key: OWB-1048
> URL: https://issues.apache.org/jira/browse/OWB-1048
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Fix For: 1.5.1
>
>
> Currently we always store our @SessionScoped beans in a Map<String sessionId,
> Map<beanbags>> in memory.
> This causes some nasty issues with sessionId rewrites. We also need the
> pretty complicated FailOver handling for enabling sane cluster behaviour.
> We do not need any of those things if we utilize the real HttpSession IF
> available. That means we do still use a mem-backed Map for owb-core, but
> provide a different SessionContext impl in the owb-web module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)