I figured that this might be the case.  Which is preferable then?  If we
leave it as-is, I could submit a patch for the sample container docs to
document the need to change this value.

~Arne


On Thu, Mar 6, 2008 at 4:23 PM, Zhen Wang <[EMAIL PROTECTED]> wrote:

> The default relay URL was changed because it broke some non-opensocial
> sample containers which pass parent parameters with a trailing slash.
>
> On Thu, Mar 6, 2008 at 4:14 PM, Kevin Brown <[EMAIL PROTECTED]> wrote:
> > Looks like an oversight. It was previously just files/container/..., but
> > that introduced issues with different parent parameters.
> >
> > I think the default value should be /gadgets/files/... so that the "out
> of
> > the box" setup is fine, and it only has to be changed if you change your
> > context path manually.
> >
> > Zhen?
> >
> >
> >
> > On Thu, Mar 6, 2008 at 4:07 PM, Arne Roomann-Kurrik <[EMAIL PROTECTED]>
> > wrote:
> > > I'm trying to put together a demo of shindig where I download the
> source
> > > from SVN, build and run the server, and display a gadget in the
> OpenSocial
> > > sample container - hopefully under 10 minutes.   Since I've been
> playing
> > > around with the sample container, I've noticed that calls to
> > rpc_relay.html
> > > are being directed to
> > >
> > >
> >
> http://<my_server>:8080/gadgets/gadgets/files/container/rpc_relay.html#..................
> > >
> > > (note the double gadgets path) which results in a 404.  I poked around
> a
> > bit
> > > and found that the "parentRelayUrl" configuration property in
> > > /config/syndicator.js is relatively pathed - prefixing a "/" provides
> the
> > > correct response (an "Unknown RPC service" error, but that's
> expected).
> > >
> > > Is there a reason for the relative path in the configuration file?  I
> > > understand that this is just for testing and will be changed in a
> > production
> > > setting, but changing it in the source will make the "out of box"
> > experience
> > > a bit smoother, IMO.
> > >
> > > Thanks,
> > > ~Arne
> > >
> >
> >
> >
> > --
> > ~Kevin
>

Reply via email to