You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/08/11 23:36:32 UTC

[jira] [Closed] (TAP5-67) Split persistence strategy into two parts: where the data is stored (session, client, hidden fields, etc.) and duration (normal, flash, maybe others)

     [ https://issues.apache.org/jira/browse/TAP5-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti closed TAP5-67.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.3

Please open a new one for 5.3 if this still applicable

> Split persistence strategy into two parts: where the data is stored (session, client, hidden fields, etc.) and duration (normal, flash, maybe others)
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-67
>                 URL: https://issues.apache.org/jira/browse/TAP5-67
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> It would be nice to be able to say "flash on the client" without having to define an entirely new strategy; it seems like the strategy (client vs. server, primarily) and the lifespan (forever, flash, maybe something new in-between, such as 'while on same page') could be split and combined in different ways.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira