[jira] [Updated] (TAP5-1276) Reference to own resourcen via external URL

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-1276:
---------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Reference to own resourcen via external URL
> -------------------------------------------
>
>                 Key: TAP5-1276
>                 URL: https://issues.apache.org/jira/browse/TAP5-1276
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Toby
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> Many websites with high traffic deliver static content such as CSS, JS or images using a CDN (content-delivery network) such as Akamai, Limelight, Level-3,CDNetworks etc...
> The principal is simply.
> static,domain.com is pointing to the CDN. The CDN requests the resources from the origin server such as www.domain.com or static-origin.domain.com and the end-user will access it via the CDN cache through static.domain.com.
> If Tapestry should actively support the integration of CDNs, it should be possible to use the standard components to reference resources externally.
> If Tapestry checks for the existence of resources or reads them for generating packages files (e.g. combine all JS or CSS files to one), it can do it locally - however the final URL should be absolutely reference by the CDN URL that can be configured.
> Example:
> @Inject
> @Path("context:images/tapestry_banner.gif")
>  private Asset banner;
> Could be extended to:
> @Inject
>  @Path("cdnContext:images/tapestry_banner.gif","http://static.domain.com/"); 
> private Asset banner;
> Alternatively it could be a global parameter to overwrite the URLs by adding an external domain for delivering CSS, JS or images.



--
This message was sent by Atlassian JIRA
(v6.2#6252)