On 12/02/2010 10:33 AM, Vega wrote: > It seems that the Vibe gadgets API does not support > gadgets.io.makeRequest - which means that the gadget should be client > side only.
We support http proxying for gadget to external URLs, and believe that gadgets.io.makeRequest is the correct call. I'm confused when you "client side only" - like wave, gadgets are JS/HTML embedded in the wave, and thus are client-side, but as mentioned should be able to make proxied-http calls. I can get someone to help debug issues. Add me (iroughley) to the message, or contact me off-list at [email protected] and I'll help resolve the issue. > > On Dec 2, 10:58 am, Georg Köster <[email protected]> wrote: >> Hi, >> I didn't have any trouble last night after the email arrived. I use the >> latest stable chrome under windows 7. >> >> Regards >> Georg >> >> On Dec 2, 2010, at 9:37, Chris Harvey <[email protected]> wrote: >> >> Yeah, I can confirm the same behaviour :( Why a sad face Chris if it worked? >> >> -- >> Chris >> iotawave.org >> Singapore >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group >> athttp://groups.google.com/group/wave-protocol?hl=en. > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
