You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gadgets often call back to services on their own servers to perform functions. There is currently no API to obtain the source URL to the gadget. This URL can be used to build relative URLs to services which exist on the server hosting the gadget.
Henry Saputra suggests:
Need to add API to get the actual gadget URL to the gadgets.util
namespace I suppose.
Shindig currently provides the non-spec'd:
gadgets.util.getUrlParameters()['url'];
But gadget developers cannot count on this.
Is the Shindig solution acceptable? If so, this may retain backward compatibility for gadget writers already using the non-spec'd Shindig solution.
Original author: [email protected] (July 25, 2012 16:19:56)
Gadgets often call back to services on their own servers to perform functions. There is currently no API to obtain the source URL to the gadget. This URL can be used to build relative URLs to services which exist on the server hosting the gadget.
Henry Saputra suggests:
Need to add API to get the actual gadget URL to the gadgets.util
namespace I suppose.
Shindig currently provides the non-spec'd:
gadgets.util.getUrlParameters()['url'];
But gadget developers cannot count on this.
Is the Shindig solution acceptable? If so, this may retain backward compatibility for gadget writers already using the non-spec'd Shindig solution.
Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1325
The text was updated successfully, but these errors were encountered: