[ https://issues.apache.org/jira/browse/TRINIDAD-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225490#comment-13225490 ]
Andy Schwartz commented on TRINIDAD-2234: ----------------------------------------- I have implemented a solution that exposes a skin pregeneration service via an internal view. Requests into this internal view cause skin pregeneration to kick in. The new API is fairly small: - A couple of system properties for enabling this service. - The internal view name. - Request parameters for tweaking pregeneration behavior. I will upload a patch shortly and provide more details on the design/implementation. > Pregeneration of skin style sheets > ---------------------------------- > > Key: TRINIDAD-2234 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2234 > Project: MyFaces Trinidad > Issue Type: New Feature > Components: Skinning > Affects Versions: 2.0.1-core > Reporter: Andy Schwartz > Assignee: Andy Schwartz > Priority: Minor > > Trinidad skinning dynamically generates style sheets at runtime to meet > context-specific (ie. platform/agent/locale/accessibility-specific) skinning > requirements. While dynamic generation of style sheets is beneficial in that > it allows fine tuning of which styles are delivered for particular contexts, > it can complicate some use cases. > One case that dynamic generation makes particularly difficult is where the > application and its resources are split across separate hosts/domains. In > this case, resources are typically hosted on a dedicated server that can be: > a) Shared across multiple applications, thus improving the likelihood of > browser cache hits. And... > b) More easily fronted by a CDN (without also having to route all application > traffic through a CDN ). > Since a single skin definition can result in an arbitrary number of generated > style sheets, it is not possible to host Trinidad skin/style sheets on a > dedicated server - ie. there is currently no reliable way to pre-generate all > possible variants of any given skin. > This issue requests that we add a new skin pregeneration feature that would > allow all style sheet variants for any skin to be generated prior to > application deployment. This would facilitate the the split > application/resources scenario described above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira