If you're using a gadget, why not use the open social container's
makeRequest call?
http://code.google.com/p/opensocial-resources/wiki/GadgetsMakeRequest

That's what it's there for...

Other alternatives include: use flash, which allows cross domain, just
for making requests, or the HTML5 cross domain ajax components.

Not sure what you're talking about with data visibility; gadget's are
not common to all users; only the gadget state object is shared; your
gadget instance talking direct to the a web service does not expose it
to other users.

~
Doug.

On Jun 19, 12:53 pm, Alex <[email protected]> wrote:
> Well, my professor told me to look for a more elegant option as she
> said option 1 is kinda like a hack to work around the SOP problem (she
> doesn't like the idea of proxy).
>
> so i would like to know which is a more elegant way to get to the
> external web service?
>
> On Jun 18, 12:18 pm, Joe Gregorio <[email protected]> wrote:
>
> > On Thu, Jun 17, 2010 at 10:35 PM, Alex <[email protected]> wrote:
> > > i have a gadget and i need to send data to a external web service for
> > > processing and get a response, currently im using JSONP to my own
> > > server and it forward the request to the external web service (the
> > > external web service reply in plain text)
>
> > > option 1)
> > > browser(gadget)-----JSONP--->MyServer-----HttpPOST---->external web
> > > service
>
> > > option 2)
> > > browser(gadget)------>Wave Server------>MyRobot----HttpPOST-----
> > >>external web service
>
> > > which option is better in the following situation and why?
> > > A)Only the viewer can see their own response from the external web
> > > service
> > > B)all participant can see everyone's response from the external web
> > > service
>
> > The visibility of the data is controlled by the gadget, so it doesn't matter
> > how the data gets to the gadget, only what the gadget does with that data.
>
> >    Thanks,
> >    -joe
>
> > --
> > Joe Gregorio
> > Developer Relations, Google Wave
>
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Google Wave API" 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/google-wave-api?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Wave API" 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/google-wave-api?hl=en.

Reply via email to