Hey Ikai, Thanks for the reply.
I'm not setting cache-control headers. I'm assuming if it was the browser, I would see the same thing locally. However, I'll test it with wget. I'll also verify that I see the problem on a different ISP when I get home. In the meantime, I'll give GAE community a shot. Thanks again, Tom On Aug 31, 12:12 pm, "Ikai L (Google)" <[email protected]> wrote: > App Engine should not automatically cache anything unless you tell it to. > Here are the probably cases: > > 1. Did you set cache-control headers? If you set cache-control:public, this > may cause your ISP, any proxies, or even the App Engine infrastructure to > hold on longer than you like. > 2. Local browser cache? (Test using curl/wget/telnet) > 3. Could your ISP be caching? > > I could be misunderstanding your email - are you using URLFetch? There may > be some caching that happens on responses, but this data should be extremely > short-lived. > > At any rate, you may want to ask this question in the Google App Engine > groups:http://code.google.com/appengine/community.html > > > > On Tue, Aug 31, 2010 at 9:38 AM, Thomas Dvornik <[email protected]> wrote: > > Hey guys, > > > I'm building an application that processes xml, which can be located > > on an external server. Based on the xml, the application views and > > runs differently. > > > A common use case when working on the xml, is to make some changes, go > > to the application, and reprocess the xml to see the changes. This > > works great locally. However, when running it on app engine, I'll make > > a change to the xml, go and reprocess it on the application, and the > > changes don't show up. If I reload the page a few time, the changes > > will show up. Modifying the url (maybe by removing www) will show the > > changes right away. Sometimes loading a different xml, then going back > > might work. > > > Does app engine automatically cache? If it does, can I stop it? Its > > weird though, because even though the changes are small, the result of > > the application is still different than before. So it seems app engine > > should be able to recognize this and not pull from the cache. Also, > > the processing is happening on the server via RPC, so caching makes no > > sense. > > > If it's not an app engine issue, can you think of anything else that > > might cause this problem or any ways to test it. I'm at a road block > > because it works great locally. > > > I might just add a bunch of logging and see if I can identify a > > problem, but figure I try to get some feedback here first. > > > Thanks guys, > > > Tom > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-web-toolkit%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog:http://googleappengine.blogspot.com > Twitter:http://twitter.com/app_engine > Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
