<Service name="my_service_name">
<Access url="../oauth-access-token" method="POST"/>
....
</Service>
It seems like iGoogle is unable to resolve such URLs relative the XML
element's base URI. As a result, it's not possible to simply author a
gadget spec and then deploy it on multiple servers. The gadget must
be modified for each server it runs on.
I noticed that in shindig's XmlUtil#getHttpUriAttribute, it expects
URIs to always have either an http or https scheme, but relative URIs
have no scheme until they are resolved against the element's base
URI. Is iGoogle inheriting this broken behavior from shindig?
--
You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group.
To post to this group, send email to
opensoc...@googlegroups.com.
To unsubscribe from this group, send email to
opensocial-ap...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/opensocial-api?hl=en.