Regarding #2, parts of the JS features have been implemented for URL
gadgets
Myspace:
http://wiki.developer.myspace.com/index.php?title=Messaging_from_an_IFra
me
eBay:
http://developer.ebay.com/DevZone/selling-manager-applications/Concepts/
SellingManagerApps_APIGuide.html#starting
iGoggle: with "limited" support for gadgets.* API, using the libs
parameter.

I wonder if there are other examples?

All of these have different methods for inclusion of the JS, which is a
problem for writing portable gadgets. I believe the most important
feature to support is RPC and dynamic height. In the future pubsub will
also be valuable. Features like makeRequest, and by extension the
OpenSocial data requests, are difficult to support due to the same
origin policy for XMLHttpRequest. But then, gadget developers choosing
to do a URL gadget can use REST and RPC.

There's an interesting proposal for OpenSocial, but not for v1.0,
regarding this:
http://wiki.opensocial.org/index.php?title=Support_iframe_model_applicat
ion_in_gadget_spec

While we have already solved this, if there is interest, I'd be
interested in working for a common solution.

Jon


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Monday, September 28, 2009 4:33 AM
To: [email protected]
Subject: Reverse proxy and URL gadgets

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]
 
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

Reply via email to