The gadget URL is needed for 3-legged OAuth requests, and is also usable for accounting purposes.
The container is passed through to allow for per-container configuration of the proxy urls, oauth callback urls, etc. On Mon, Dec 27, 2010 at 10:07 PM, Da Wei Wang <[email protected]> wrote: > No, it is core.io.makeRequest to retrieve remote content. In this > function implementation, the gadget instance related data (gadget iframe > url, gadget container, > > gadget synd, gadget nocache flag) is passed to makeRequest servlet via > XHR. I am not sure why gadget instance is used during remote content > retrieval. > > Best regards, > Da Wei Wang(王大炜) > Email: [email protected] Tel: 86-10-82452636 > 北京市海淀区东北旺西路8号 中关村软件园28号楼 寰宇大厦 邮编：100193 > [image: Inactive hide details for Henry Saputra > <[email protected]>]Henry > Saputra <[email protected]> > > > > *Henry Saputra <[email protected]>* > > 2010-12-28 11:58 > Please respond to > [email protected] > > > > To > > [email protected] > cc > > > Subject > > Re: How Shindig core.io.makeRequest use gadget instance information > > Are you talking about getting gadget metadata request? > > - Henry > > On Mon, Dec 27, 2010 at 6:31 PM, Da Wei Wang <[email protected]> wrote: > > > > > > Hi, > > > > I find in core.io feature, gadgets.util.getUrlParameters is invoked to > > get some gadget instance information (gadget iframe url, gadget > container, > > gadget synd, gadget nocache flag), then these information are passed to > > server as http request parameter in one core.io.makeRequest invocation. I > > am not sure how Shindig makeRequest servlet make use of these > information. > > In concept, gadget instance is not related with remote content retrieval. > > > > Any one could explain the design purpose? Thanks. > > > > Best regards, > > > > -- > Thanks, > Henry > > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner
