On Dec 4, 3:44 am, "Reinoud Elhorst" <[EMAIL PROTECTED]> wrote:
> 3) You haven't made a case why you need url contenttype. If you need pages > rendered on some server, just retrieve them using ajax and display them Network topology. The social network I'm building has some gadgets I want to host behind a firewall. Someone who is behind the firewall can access the gadget; someone who isn't, can't. For example, I'd like to allow a gadget that can access some resource that a corporation wants to guard. (Corporate calendar, email system, whatever.) I realize there are ways to hack around this (like creating a public proxy server that can reach behind the firewall, or using "JSONP" <script> tag fetches from the UA to defeat cross-domain restrictions), but those have security consequences. Namely, let's say we consider the gadget to be "trusted", but the container to be "untrusted". Since the gadget is trusted, we assume that it won't attempt to compromise security and leak information. Since the container is not trusted, we cannot make the same assumption. Anyway, I'm just trying to get a sense of what folks are thinking in this direction: I realize I'm going to have to invent my own solution for a while. I just want that solution to be in the same general vicinity as the finalized OpenSocial. :) thanks! chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
