Hi Alex, the gadget server for rendering must be on another server then the container server for security reason: this way the application won't be able to access data(for example cookies) of the container. This is a simple consequence of the browser security architecture: if you have a page in domain1.com that has an iframe pointing to domain2.com, the iframe window will not be able to access any data in parent window domain1.com.
On 12 Giu, 18:27, Alex <[EMAIL PROTECTED]> wrote: > From what I can tell, the structure of OpenSocial containers is to > have the container server itself, a gadget server for rendering, and > server for individual apps. First off, am I understanding this > correctly? And secondly, if I am can someone please explain why the > gadget server and the container server can't be one in the same? What > makes this implementation necessary? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en -~----------~----~----~----~------~----~------~--~---
