[
https://issues.apache.org/jira/browse/SHINDIG-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561657#action_12561657
]
Kevin Brown commented on SHINDIG-28:
------------------------------------
The only urls that the gadget server is explicitly aware of are the other
servlets (/proxy and /js, neither of which are serving static content) and
ifpc_relay.html, which MUST be served from the same domain as the gadget. You
could possibly use a CDN to cache /js, but that is already configurable by
setting the js-service-path configuration variable in web.xml (it defaults to
js/, you could always change it to http://cdn.example.org if you want).
Currently there's no built in cache busting, but it's on a todo list, somewhere
I'm sure.
The other static files (stuff in javascript/) aren't ever referenced by the
gadgets server, and are only included for unit and compliance testing. Rolling
them into webapp/ is for development -- real sites would use their own data for
actual deployments, and implementing such functionality is well beyond the
scope of the shindig project.
> Allow a URL prefix for all static content to allow for use on CDNs
> ------------------------------------------------------------------
>
> Key: SHINDIG-28
> URL: https://issues.apache.org/jira/browse/SHINDIG-28
> Project: Shindig
> Issue Type: New Feature
> Components: Features
> Reporter: Paul Lindner
> Assignee: Kevin Brown
>
> For static content we should allow a URL prefix to allow serving up this
> content from a CDN like Akamai.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
