Hi Jason: First off, it sounds like you're on the right track to me. A few notes:
1. If you're hosting gadgets on gadgets.site.com, you should make absolutely sure that any "important" (however you define this) cookies are stored only on www.site.com, *not* on .site.com. Ideally no cookies should be sent to any given gadget render. 2. Shindig doesn't yet have an OpenSocial JS implementation that uses the RESTful APIs. You're welcome to implement and contribute one though :) 3. I'm not 100% clear on what you mean by where you're supposed to set VIEWER and OWNER. These are passed in as hash-params to the gadget IFRAME, for instance. Is that what you mean? John On Wed, Apr 30, 2008 at 1:21 PM, Jason Burgess <[EMAIL PROTECTED]> wrote: > Now that I've got a working gadget server and some basic functionality. I > seem to be getting lost in the documentation for connecting my site's data > to it. > > > > Here's what I *think* is going to work based on what I've read. Please > correct me where I'm wrong. And there are still a few pieces of the puzzle > I'm missing, but I'll point them out along the way. > > > > I've got a main website, www.site.com, and a gadgets server, > gadgets.site.com. > > > > On gadgets.site.com, /gadgets is transparently proxied to the jetty > server, > while /social is transparently proxied back to www.site.com/social, so > that > gadgets.site.com believes it is coming from the same server. > > > > On /social/data, I'm implementing the RESTful API to retrieve data from the > main website's database. > > > > From what I understood, shindig will mediate between the RESTful API and > the > gadgets, but most of that isn't finished yet. > > > > From www.site.com, I'm implementing the container to call gadgets.site.com > to render the gadgets. > > > > One thing I'm still having trouble discerning is where in the container I'm > supposed to be setting VIEWER and OWNER. > > > > Hopefully, I'm at least headed in the right direction here. > > > > Jason > >
