tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Created: (TAPESTRY-637) Application state objects are stored back to the session, even if unchanged
Date Sat, 10 Sep 2005 14:19:30 GMT
Application state objects are stored back to the session, even if unchanged
---------------------------------------------------------------------------

         Key: TAPESTRY-637
         URL: http://issues.apache.org/jira/browse/TAPESTRY-637
     Project: Tapestry
        Type: Improvement
  Components: Framework  
    Versions: 4.0    
    Reporter: Howard M. Lewis Ship
 Assigned to: Howard M. Lewis Ship 
    Priority: Minor


Any read access to an ASO will cause the ASO to be stored back into the session at the end
of the request.

It would be nice if there was a way that this could be avoided when the ASO's internal state
is unchanged.

The obvious implementation is to have an optional interface implemented by ASOs for this purpose.
 The "dirty flag" would be cleared when the ASO is stored into the session (i.e., the ASO
would also implement HttpSessionBindingListener and clear the flag in valueBound()).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message