Bullet point #6c of section 3.1.3 - Compliance: Gadget Server - Process; of the Gadgets API Specifiction describes one method: http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/Gadget s-API-Specification.html#process iGoogle originally implemented this.
-----Original Message----- From: Kevin Brown [mailto:[email protected]] Sent: Tuesday, September 29, 2009 10:05 PM To: [email protected] Subject: Re: Reverse proxy and URL gadgets On Mon, Sep 28, 2009 at 4:32 AM, <[email protected]> wrote: > Hi, > > Working with Shindig we have come across some use cases for which we > modified shindig code base. > > 1. For URL gadgets shindig do redirect to the gadget URL, however in > the reverse proxy it's an issue for web masters. So we have modified > that part to respond as HTTP 200 (no redirect). > > 2. Why shindig does not support the JS features for URL gadgets? [One > reason could be cross site scripting but in *a company setup* with > *reverse > proxy* this can be useful feature to have] > What do you mean by "support"? How would shindig "support" getting the JS code into the third-party iframe? > > 3. Request parameter passing to all gadgets - We have modified Shindig > to pass all the request parameters to the gadgets in a page. > > We have these features implemented, we love to get an opinion of the > community regarding these changes. > > Thanks, > > Samik > > Please do not print this email unless it is absolutely necessary. > > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > addressee(s) and may contain proprietary, confidential or privileged > information. If you are not the intended recipient, you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately and destroy all copies of this message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of > viruses. The company accepts no liability for any damage caused by any > virus transmitted by this email. > > www.wipro.com >
