On Feb 4, 2008 9:59 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > This puts too much burdeon on potential consumers of Shindig to have to > place app data server logic into the gadgets server. We've been > intentionally avoiding this from the beginning. The GadgetServer shouldn't > be required to know anything about the app data server. All communication > with the app data server can happen over the proxy (if on a different host > name), directly within the gadget via XHR if on the same host, or over IFPC > (in the container mediated model). The security token is an opaque string > that is simply passed on in this case. The only time the gadget server > actually does anything with the security token is when it is being used for > operations like locking down the open proxy.
You've lost me. Can you give me some details on how this would work, for either the IFPC or the proxy model? In particular: - how would setprefs be implemented? - how would phone home be implemented? - how would locked domains be implemented? Cheers, Brian
