Why? Because its the only way. Assume siteA is google.com and its where the app is hosted. The app devolver wants to make a request to hisite.com which is SiteB. So the only way for siteA to access siteB and receive response is using a server-sided proxy. The other way would be to use js ajax requests but there is the cross site security issue that will block you from doing it. Plus I don't think google are going to "log" whats being sent thru their servers....wait, nvm, they log everything else so you probably don't have anything left to hide.
On Nov 11, 11:46 am, siegi <[EMAIL PROTECTED]> wrote: > As far as I understand any data transfered from the module definition > source and further loads and ajax calls (_IG_Fetch*) is passed or > filtered through a proxy box. > > If that is the case then any data is sent to somewhere which is > neither controlled by the social network nor by the gadget developer. > > Why is the system designed like this? Who wants to peek every bit > requested from any gadget? > > With respect to performance this also not the best solution. > > I would rather allow direct client gadget communication or filtering > through the social network servers but no filtering by third party > servers. > > Hopefully, I simply did not understand the system architecture right > and someone from the builders could drop me a correction or an > alternative method. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" 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/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
