hmm. If I am not mistaken - by default, makeRequest calls are not
cached.

On Oct 13, 2:08 pm, "Swapnil Shinde" <[EMAIL PROTECTED]> wrote:
> My understanding is that the caching works around any API calls you make
> using makeRequest. So it might call the API everytime and just return the
> contents of the API response from Google cache. Now for caching the images,
> you should be adding an expires header on them, so that they browser can
> cache them in it's cache.
> Swapnil.
>
> On Mon, Oct 13, 2008 at 11:57 AM, JSON <[EMAIL PROTECTED]> wrote:
>
> > Does gadgets.io.getProxyUrl function get the URL of cached copy or
> > does it also cache it if the file is not already cached?
>
> > On Oct 13, 1:55 pm, JSON <[EMAIL PROTECTED]> wrote:
> > > I wonder if the content-rewrite tags are supposed to work only for
> > > img tags in the XML file (Application Spec) and not for the data
> > > returned by a makeRequest. Our images are rendered from the response
> > > of a makeRequest. Is that the reason?
>
> > > On Oct 10, 5:01 am, JSON <[EMAIL PROTECTED]> wrote:
>
> > > > Hello,
>
> > > > We have the following code for content-rewrite in our app:
>
> > > >http://www.orkut.com/Application.aspx?appId=928144150139
>
> > > > <Optional feature="content-rewrite">
> > > > <Param name="include-urls">.*</Param>
> > > > <Param name="exclude-urls"/>
> > > > <Param name="include-tags">img,link,script</Param>
> > > > </Optional>
>
> > > > Looking at server logs, we are finding that the code is not working -
> > > > since we are getting repeated GET calls for static image content.
> > > > Please advise.
>
> > > > ~ JSON
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Orkut Developer Forum" group.
To post to this group, send email to opensocial-orkut@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/opensocial-orkut?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to