Hi, See section 14.9 here, http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html, for details on cache control headers. Depending on how long it's OK to cache, you probably want to either set max-age or private.
You can set a header on responses from your App Engine app as outlined here: http://code.google.com/appengine/docs/python/tools/webapp/redirects.html (for Python and webapp). If you're using Java, or Python with a different framework, the answer will probably be similar, but I don't have an answer off the top of my head. Dan On Aug 28, 6:25 pm, DayDreamer <[email protected]> wrote: > First of all, thank you for answering. > I'm sorry it took me a while to answer, I only now found my post in > this forum. > > For your question, I was referring to your first guess: updating data > in my App Engine app, and pulling it to my gadget. > > I tried you "cache-busting parameter" idea and it worked! You possibly > saved our project, so thank you very much. > > I just want to ask one more thing: is there a quick way to disable the > cache, instead of adding a parameter to every request? > What was that you said about setting cache headers in my App Engine > app? How do I do that? > > Thank you! > > On Aug 24, 9:30 pm, "Dan (Google)" <[email protected]> wrote: > > > Hi, > > > I'm not entirely sure how to answer your question, as it can be > > interpreted in two different ways (which have different answers). If, > > when you say "updatethe data on the server", you are referring to > > updating data in your App Engine app, and pulling it into your gadget, > > it's possible this data is being cached. There are several ways to > > circumvent these caching mechanisms. The recommended approach would be > > to set cache headers in your App Engine app, if the data should be > > public. If the data is private, you should send a signed makeRequest > > to App Engine from your gadget, which will not be cached. Finally, you > > can append a cache-busting parameter (foo=some_random_number) to your > > request URL. > > > If, instead, you mean that your App Engine app sends updates to > > appdata within the gadget, there are known delays, but should not be > > as long as a day. Please let me know if this is what you are seeing. > > > Thanks, > > Dan > > > On Aug 23, 11:51 am, DayDreamer <[email protected]> wrote: > > > > We started a Gadget that uses a server we started on appengine and its > > > database, and it also uses open-social to find out about friends of > > > the current user. > > > Only recently we encountered a problem... > > > > After weupdatethe data on the server (add\delete\modify) and refresh > > > the page, it does not show the updated data- it shows the old > > > information. When we check the information on the server - we see it > > > is as it should be. It has the updated information. But our gadget for > > > some unknown reason gets the old data instead of the new one. > > > > Note: we are working on the sandbox and we removed the gadget's cache > > > option. > > > > Only after a while (I don't know exactly... It could be a few hours > > > and it could be a day, I don't know yet) it shows the real data. > > > > I can't ignore this situation. It would not be a friendly interface, > > > and it could cause unnecessary bugs. > > > > What can I do to resolve this? Is there another cache I don't know > > > about? Are there server-problems on appengine? Anupdateon javascript > > > that causes the site to get the old data? > > > > Thank you in advance- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
