Scenario three is a reasonable approach and that's how most of the Social networking sites run.
Your deployment can look as below: Server1 (Domain X) ------------ Shindig Server Common Container index.html or your webpage that bootstraps container and your page etc.. Server 2 (Domain Y) ------------- Your custom webapp Other gadget apps Hope it helps. Thanks and regards Kris Vishwanathan |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Davies,Douglas" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |<[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Cc: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Davies,Douglas" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |03/29/2011 02:35 PM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Shindig and webapp on same host/domain or not? | >--------------------------------------------------------------------------------------------------------------------------------------------------| I want to follow up with an earlier thread I had about webroot that has taken me a different direction. Sorry for starting a new thread, but the listserv (or stupid entourage on the mac) is making it so that my messages have been posted as 'daviesd' and not '[email protected]' and this seems to be affecting the delivery and even the web view of the archive. Anyway... I need some assistance as far as how shindig and the application webapp using shindig to render embedded gadgets should be deployed. I've successfully gotten shindig running along-side my application webapp that uses it. Both projects are their own war file and deployed to the same server (and thus same fully qualified domain name). The shindig war has been patched to use the /shindig web context and the application war runs as root. So /index.html is the page that includes the common container javascript and references /shindig/gadgets, etc. Is the desired deployment architecture: 1. Add shindig as part of an existing webapp 2. As a separate webapp on the same host/domain (as I've done) 3. Or as a separate webapp on a totally different host/domain (so the application runs at www.mydomain.com and shindig runs at www.myshindig.com). I'm able to get things to work fine with scenario 1 and 2. Scenario 3 is where I have problems. The common container doesn't seem to support shindig on a different host/domain then the webapp using it. If I deploy shindig to a different host and run my webapp locally, I see it trying to use http://localhost:8080/shindig/rpc instead of http://www.myshindig.com/shindig/rpc). It appears the javascript apis are using relatives paths based on the current browser host. On top of all this I've seen various threads about security concerns as to where the gadget is running. In scenarios 1 and 2 it possibly has access to private information in the webapp that is using it. In scenario 3 it's running in an isolated shindig farm and any malicious activity would only affect those servers but not the main application. As I've said in the previous thread... I might be totally misunderstanding this. I really want to push for scenario 3, but if it's not supported in the common container (or in shindig at all) as this thread suggests http://mail-archives.apache.org/mod_mbox/shindig-dev/201102.mbox/%3cAANL [email protected]%3e then I'm willing to at least settle for scenario 2, assuming there are not security concerns there. Thanks, Doug Davies OCLC, Online Computer Library Catalog
