You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2008/03/29 12:52:24 UTC
[jira] Updated: (SHINDIG-162) Simple proxying should take advantage
of the browser cache
[ https://issues.apache.org/jira/browse/SHINDIG-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner updated SHINDIG-162:
---------------------------------
Component/s: OpenSocial - Javascript
Gadgets Server - Java
Description:
Right now even the simplest proxy request will result in a POST request to the proxy server endpoint.
This is terrible for perfromance since even cached content will not be cached at the browser level.
I propose that we change gadgets.io.makeRequest() to use GET requests wherever possible. Especially for the _IG_FetchContent() and _IG_FetchXmlContent() cases.
We also need to modify the proxy servlet to disregard existing expires and cache-control headers. iGoogle will override Cache-Control private and substitute Cache-Control max-age=3600
Double bonus points if this can be done this weekend !
was:
Right now even the simplest proxy request will result in a POST request to the proxy server endpoint.
This is terrible for perfromance since even cached content will not be cached at the browser level.
I propose that we change gadgets.io.makeRequest() to use GET requests wherever possible. Especially for the _IG_FetchContent() and _IG_FetchXmlContent() cases.
Double bonus points if this can be done this weekend !
> Simple proxying should take advantage of the browser cache
> ----------------------------------------------------------
>
> Key: SHINDIG-162
> URL: https://issues.apache.org/jira/browse/SHINDIG-162
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java, OpenSocial - Javascript
> Reporter: Paul Lindner
>
> Right now even the simplest proxy request will result in a POST request to the proxy server endpoint.
> This is terrible for perfromance since even cached content will not be cached at the browser level.
> I propose that we change gadgets.io.makeRequest() to use GET requests wherever possible. Especially for the _IG_FetchContent() and _IG_FetchXmlContent() cases.
> We also need to modify the proxy servlet to disregard existing expires and cache-control headers. iGoogle will override Cache-Control private and substitute Cache-Control max-age=3600
> Double bonus points if this can be done this weekend !
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.