Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Date: Mon, 23 Sep 2013 09:18:03 +0000 (UTC)
From: "Thomas Andraschko (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Message-ID: <JIRA.12669986.1379913161818.1932.1379927883219@arcas>
In-Reply-To: <JIRA.12669986.1379913161818@arcas>
References: <JIRA.12669986.1379913161818@arcas>
Subject: [jira] [Commented] (MYFACES-3779) Mixed mode(Server+client) for
 state saving
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Andraschko commented on MYFACES-3779:
--------------------------------------------

>> It is clear that the hack proposed aims to solve some situations where a ViewExpiredException should not be thrown.

I didn't know that ViewScoped beans will be always serialized to the session now.
What happens in the future if i would use client side state and the ViewScoped beans are not available anymore? Also a ViewExpiredException?

                
> Mixed mode(Server+client) for state saving
> ------------------------------------------
>
>                 Key: MYFACES-3779
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3779
>             Project: MyFaces Core
>          Issue Type: New Feature
>            Reporter: Ertio Lew
>
> How about having a mixed mode for state saving whereby state is initially kept on server for a configurable amount of time (so that fast frequent requests are served without transferring the state from client to server several times, the drawback with client side saving) & after that period of time if the page is still alive in browser but it is idle, a javascript request is triggered which asks the server for that state data & now it will be kept on client side, now the client & the server both know that state for this session is there on client. If the page has died & no request has been sent to server asking for state data till that period of time, then state data would be removed from server.
> A further enhancement could be that you could set a fixed amount out of all memory on server that you want to allocate for state saving of all sessions. Till the time that quota remains, state is kept on server using that quota. But when that quota is over all the state information for further sessions is kept using client side state saving. Also a mixed mode.
> Such mixed modes would be very helpful in improving performance, & better utilization of the server resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira