You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Igor Drobiazko (JIRA)" <ji...@apache.org> on 2010/11/03 17:48:24 UTC
[jira] Created: (TAP5-1335) Make the caching logic inside
PageSource service more flexible
Make the caching logic inside PageSource service more flexible
--------------------------------------------------------------
Key: TAP5-1335
URL: https://issues.apache.org/jira/browse/TAP5-1335
Project: Tapestry 5
Issue Type: Improvement
Affects Versions: 5.2.2
Reporter: Igor Drobiazko
Currently the cache key for pages consist of the the page name and the locale.
It would ne really nice to have a funcionality which makes possible to provide application specific cache keys.
The use case is that for modern web applications the locale is no longer a unique classifier for a page. I need to load different instances of a page for different mobile devices.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Closed] (TAP5-1335) Make the caching logic inside
PageSource service more flexible
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-1335.
--------------------------------
Resolution: Won't Fix
Tapestry 5.3 has theme and skinning support.
> Make the caching logic inside PageSource service more flexible
> --------------------------------------------------------------
>
> Key: TAP5-1335
> URL: https://issues.apache.org/jira/browse/TAP5-1335
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.2.2
> Reporter: Igor Drobiazko
>
> Currently the cache key for pages consist of the the page name and the locale.
> It would ne really nice to have a funcionality which makes possible to provide application specific cache keys.
> The use case is that for modern web applications the locale is no longer a unique classifier for a page. I need to load different instances of a page for different mobile devices.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1335) Make the caching logic inside
PageSource service more flexible
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-1335.
--------------------------------
Resolution: Won't Fix
Tapestry 5.3 has theme and skinning support.
> Make the caching logic inside PageSource service more flexible
> --------------------------------------------------------------
>
> Key: TAP5-1335
> URL: https://issues.apache.org/jira/browse/TAP5-1335
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.2.2
> Reporter: Igor Drobiazko
>
> Currently the cache key for pages consist of the the page name and the locale.
> It would ne really nice to have a funcionality which makes possible to provide application specific cache keys.
> The use case is that for modern web applications the locale is no longer a unique classifier for a page. I need to load different instances of a page for different mobile devices.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira