These are theories, haven't tryed yet: 1- Your openlayers application will be in a view (most likely a web page) 2- There will be another application in another domain 3- Another webpage(application) will want to access your webpage to embed your application in itself (here cross domain issue happens) 4- so it will be like --------------------------------------------- l Another web page (www.otherapp.com) l ------------------------------------ l l Your openlayers app l l (www.yourapp.com l ------------------------------------- l ---------------------------------------------
As a solution I can suggest 2 ways: 1- Your domain can accept another application's domain to request and serve its application view: a- you will have a view b- you will allow cross domain to other domain: http://enable-cors.org/server.html c- other domain will embed your view into its own view http://jsfiddle.net/7MaXx/ http://stackoverflow.com/questions/924946/use-of-iframe-or-object-tag-to-embed-web-pages-in-another 2- Your domain will not accept cross domain requests but other website will bring your application view through its own server a- other application requests view from its own domain (mapPage for example) b- other application's controller requests your openlayers application in serverside (or apache modproxy?) c- controller serves embedded view to client d- client embeds that view into its own view Hope that helps -- View this message in context: http://osgeo-org.1560.n6.nabble.com/OpenLayers-app-on-another-site-tp5028264p5028275.html Sent from the OpenLayers Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
