Hi Daniel -
Gadgets must be hosted on a public server, as they are sent through a proxy on the gadgets container server to get rendered. I thought we put that restriction in the docs, but perhaps it needs to be made more prominent. You may want to try hosting the XML publicly, and referring to your local server files in scrript tags .
- pamela
--
You received this message because you are subscribed to the Google Groups "Google Wave API" group.
To post to this group, send email to google-...@googlegroups.com.
To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
Cheers,
Paul
On Jan 27, 9:36 am, pamela fox <pamela....@gmail.com> wrote:
> Hi Daniel -
>
> Gadgets must be hosted on a public server, as they are sent through a proxy
> on the gadgets container server to get rendered. I thought we put that
> restriction in the docs, but perhaps it needs to be made more prominent. You
> may want to try hosting the XML publicly, and referring to your local server
> files in scrript tags .
> - pamela
>
> On 27 Jan 2010 23:39, "Daniel França" <daniel.fra...@gmail.com> wrote:
>
> Hi,
> I'm trying to host a local gadget running Apache,
> when I try to access that via browaer it works fine (and even work inside my
> company network), but in Google Wave the gadget appears broken, and I don't
> have any tip about why it's happening (Or I don't know where to see that).
>
> The same gadget XML gadget file works fine when it's hosted in Google
> Hosting.
>
> Any hint about how can I find out what's happening here?
>
> Best Regards,
> Daniel C. França
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Wave API" group.
> To post to this group, send email to google-...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-wave-a...@googlegroups.com<google-wave-api%2Bunsu...@googlegroups.com>
The actual XML is fetched through the gadgets proxy. Anything else
referenced in the gadget should be fetched by the browser, same as a
normal webpage.
If you want to share your gadget with the world one day, every aspect
will need to be public (same as a webpage).
- pamela
> To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
I followed all the guideline on the Get Started page for building a
Wave Gadget. The section "Running a Gadget talks about hosting on GGE
and SVN". I tried hosting with GGE. Even though the file was uploaded
successfully, I wasn't redirected to any syndication creator page as
instructed in the "Publishing Your Gadget from GGE section".
Also, I don't seem to see any difference between hosting on GGE and
SVN. It seems both links to the same page.
I don't know what I'm doing wrong. Could you help shed more light.
On Jan 31, 11:09 am, "pamela (Google Employee)" <pamela...@gmail.com>
wrote:
> This section talks about thegadgetbeing publicly visible:http://code.google.com/apis/wave/extensions/gadgets/guide.html#hello
>
> The actual XML is fetched through the gadgets proxy. Anything else
> referenced in thegadgetshould be fetched by the browser, same as a
> normal webpage.
>
> If you want to share yourgadgetwith the world one day, every aspect
> will need to be public (same as a webpage).
>
> - pamela
>
>
>
> On Fri, Jan 29, 2010 at 5:38 AM, rocketman <pbar...@gmail.com> wrote:
> > Pamela, could you clarify or point to the docs that show what part(s)
> > of aGadgethave to be hosted on a public server? Does the actual
> >Gadgetcode have to be exposed publicly?
>
> > Cheers,
> > Paul
>
> > On Jan 27, 9:36 am, pamela fox <pamela....@gmail.com> wrote:
> >> Hi Daniel -
>
> >> Gadgets must be hosted on a public server, as they are sent through a proxy
> >> on the gadgets container server to get rendered. I thought we put that
> >> restriction in the docs, but perhaps it needs to be made more prominent. You
> >> may want to try hosting the XML publicly, and referring to your local server
> >> files in scrript tags .
> >> - pamela
>
> >> On 27 Jan 2010 23:39, "Daniel França" <daniel.fra...@gmail.com> wrote:
>
> >> Hi,
> >> I'm trying to host a localgadgetrunning Apache,
> >> when I try to access that via browaer it works fine (and even work inside my
> >> company network), but in Google Wave thegadgetappears broken, and I don't
> >> have any tip about why it's happening (Or I don't know where to see that).
>
> >> The samegadgetXMLgadgetfile works fine when it's hosted in Google
> >> Hosting.
>
> >> Any hint about how can I find out what's happening here?
>
> >> Best Regards,
> >> Daniel C. França
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Google Wave API" group.
> >> To post to this group, send email to google-...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> google-wave-a...@googlegroups.com<google-wave-api%2Bunsubscribe@ googlegroups.com>
On 31 янв, 17:09, "pamela (Google Employee)" <pamela...@gmail.com>
wrote:
Most gadget containers also provide methods of sending other content
through the proxy, for caching purposes.
All io.makeRequests call also go through proxy.
- pamela
But need more clarifications.
In context of wave - what is the wave server - gadget server, proxy or
container?
And is gagets.io.makeRequest available in wave?
What other opensocial features supported in wave?
On 8 фев, 08:21, "pamela (Google Employee)" <pamela...@gmail.com>
wrote:
Google Wave (wave.google.com) is the container server. When it embeds
gadgets, it uses another gadget server (gmodules.com).
That gadget server proxies the XML and converts it into HTML. It also
proxies any requests through gadgets.io.makeRequest() or
gadgets.io.getProxyUrl().
Wave supports the standard gadgets.* API methods
(http://code.google.com/apis/gadgets/docs/reference/).
For gadgets.io.makeRequest, we support requests for external data, but
not social data from the container.
- pamela