Just make that "token" part of the URL that you use in your requests. Now different users have different URLs for those Ajax calls, and caching won't cause them to be mixed up.
On Tue, May 4, 2010 at 9:41 PM, Marcelo de Moraes Serpa <[email protected] > wrote: > Hi list, > > Considering XMLHttpRequests can't be done across domains, and that one has > to use gadgets.io.makeRequest to make the request through a Google proxy, I > would like to know -- are multi-user applications viable on the Google > Gadgets/OpenSocial. (i.e any app that needs to fetch data from a web server > and that uses a token to get content specific to the user that configured > the gadget). > > What I'm affraid of is that the caching behavior could interfer with a > multi-user gadget, showing something that the user should be shown to the > user. > > Would that be a problem? > > Thanks in advance, > > Marcelo. > > -- > 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]<google-gadgets-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/Google-Gadgets-API?hl=en. > -- 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.
