Shindig Dev Team:
Practically speaking, does the gadgets container page have to be served
from the Shindig server's domain to utilize the osapi?
I do see that osapi is generally made available in the new common
container, but I am using the old shindig container support since it
handles chrome and other things that do not appear to be available in
the common container yet. I am also following guidelines from the wiki
that strongly suggest the container/page domain be different than the
shindig/gadgets domain. Thus, some complexities seem to arise.
What I am after is an additional osapi service I can use from the
container, (e.g. a preferences service that can integrate with a client
side container UserPrefs implementation). However, when I try to include
the osapi service when I load the container javascript, it adopts the
domain of the page which is not the same as the Shindig server's domain.
I do see where the configuration can be changed from "%host%" to
something more specific, but this would then appear to result in a cross
domain XHR request. Of course, that might be fine in a CORS world, but I
am wondering if I am headed in the right direction at this point?
Any advice more than welcome! Thanks in advance,
Randy Watler
