Hello. I¹m new to this listserv, so please correct any protocol/etiquette
mistakes I might make.

I¹m pretty new to opensocial and shindig.  I¹ve played around with bringing
the war file down and renaming it ROOT.war.  I¹ve also played around with
creating a new webapp application archetype and just pulling down the maven
artifacts.  The issue I¹m struggling with (and I¹ve seen references to it on
this group) is the root web app v.s. non-root webapp approach.  It would
appear to me that since through 1.0, 2.0, and now 3.0 the root deployment
nature of shindig hasn¹t changed, that this is the desired approach.
However I see many references to people patching container.js and
shindig.properties to get it to run in a different web context.  I would
think the later is the more common case, but I might be missing something.
The fact that there isn¹t just 1 location to change the context (and besides
the fact that localhost is referenced all over the place) steers me into
thinking the architects did not intend for this scenario however.  But then
again, this is a reference implementation for us to change as required.

Then a co-worker pointed me to this article

http://www.freesoftwaremagazine.com/columns/opensocial_overview_how_opensoci
al_works_and_integrate_with_cms

And asked if I inferred from this that the javascript container code should
be installed on one server while the shindig server should be installed on
another (for security reasons???).  My thought was is I¹d build a
shindig.war that was specific to our needs and allow anyone to drop this
into there current environment.  I was envisioning it on the same host so
that the javascript and server were both deployed together and the webapp
could just reference /shindig/gadgets, etc.  All the hosting webapp would
have to do is define the DIV elements that want to render into and provide
some database setup for persistence.  What is the drawback of this approach?
What is the preferred approach?  I hope this makes sense.

One other thing... If anyone is aware of consultants/contractors that are
shindig experts, I¹d be interested in talking to them about a possible stint
at our company to help steer us in the right direction.

Thanks,

Doug Davies
OCLC, Online Computer Library Catalog

Reply via email to