Part of the makeRequest call is a time-to-cache. http://code.google.com/apis/opensocial/articles/makerequest-0.8.html#caching
Unless I've managed to totally confuse myself, you should be able to pull data from the app server, and then cache it for, say, 15-120 seconds (depending on taste), meaning that it's still fresh, but should the user reload the page during that time, it'll pull from the local cache instead of beating the App Server to death. On Mon, Jan 12, 2009 at 3:56 PM, Citron, David <[email protected]> wrote: > Er, makeRequest sends requests back to the app server, though--the very > machine we're trying to unload. We wanted to avoid hitting our app > server every time someone refreshes iGoogle, for e.g. > > There are only two logical machines in play here--the gadget container > (Shindig--the persistence host) and the app server (the makeRequest > host), correct? Am I missing something? > > Thanks, > Dave > > -----Original Message----- > From: Chewy Trewhella [mailto:[email protected]] > Sent: Monday, January 12, 2009 10:52 AM > To: [email protected] > Subject: Re: Compressing appData before persistence -- 10K is not enough > > > > > I suppose we were (naively) hoping that we would be able to use gadget > > persistence to cache previously-retrieved application data, thus > > reducing the load on our app server during simple page reloads and the > > like. That's why I was investigating potentially Deflating the data or > > employing some other kind of compression, though with only 10K per > > gadget*user, even that probably won't be sufficient. > > > Won't makeRequest do this? >
