Rrrrrright. I suppose not. I'm stuck in the following mental trap that I hope you can help me out of:
We have a container that is not hosted on the same machine as the Shindig server. Therefore, I cannot make AJAX calls from the container to the Shindig server to generate the iframe. This applies to "output=js" and to the metadata servlet. I got confused into thinking that "output=js" would somehow help me, but of course it doesn't. So, the only solutions that come to mind are: 1) Server-side (servlet-based) aggregation a la Liferay Gadgets Portlet - requires a dynamic Web server and we hope to deploy our container on a static Web server 2) Reverse-proxy the Shindig server to a URL on the container's host (is this what iGoogle sandbox does or do they just have their own custom servlet?) - requires the reverse proxy 3) Create my own iframe by hand or via JavaScript that happens to have the correct URL for the IFR gadget servlet - brittle? Thanks so much for your input or even just a pointer to where this question might already be answered. I've searched around but haven't found exactly what I'm looking for (or haven't realized it). -Dave -----Original Message----- From: Kevin Brown [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 12:35 PM To: [email protected] Subject: Re: What happened to "output=js"? On Wed, Nov 26, 2008 at 6:10 AM, Citron, David <[EMAIL PROTECTED]> wrote: > Thanks! So what are the recommended better ways to implement the > functionality that "output=js" used to support? Is there anything that output=js gave you that the metadata servlet does not? > > > -Dave > > -----Original Message----- > From: Michael Hermanto [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 25, 2008 4:55 PM > To: [email protected] > Subject: Re: What happened to "output=js"? > > > When inserting a gadget in a container not hosted on the same domain > as > > Shindig, it's convenient to be able to dynamically generate the JS to > > create the gadget iframe. > > > > > > > > I noticed that the non-sandbox gmodules.com supports an "output=js" > > request parameter that does just that, but Shindig does not support > such > > a parameter. > > > > > > > > What's the history of the "output=js" parameter, why doesn't Shindig > > support it, and what's the recommended alternative? > > > > You're correct to say that "output=js" is not supported by Shindig. It > is > used by www.gmodules.com to render open-syndication gadgets (or gadgets > for > your webpage, here <http://www.google.com/ig/directory?synd=open>). I > understood that there are better ways to support "output=js", so it > probably > should not continue in Shindig. >
