Re: [Google Wave APIs] Re: State change

2009-12-08 Thread Avital Oliver
You're right - you can't do any regular AJAX calls. All AJAX calls must
respect the same-domain restriction. Instead, use a JSONP-like mechanism (a
hack involving embedding a script tag by the DOM to load a server-side
generated script with the information needed)

--
http://wave.theWE.net
http://twitter.com/theWE_



On Tue, Dec 8, 2009 at 1:26 AM, Dan dansmithw...@googlemail.com wrote:

 Does that have implications for server side interaction as well?  i.e.
 Would this cause a cross domain conflict during an Ajax call to the
 server?

 I should try it, I know, but hopefully someone else already has.

 --

 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-wave-...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://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 google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.




Re: [Google Wave APIs] Re: State change

2009-12-06 Thread Avital Oliver
Gadgets are executed in iframes with variable domains (something like
*-opensocial.google.com where * can be any number). Cookies are stored
on a per-domain basis, so you may or may not be able to read the
cookie you stored once you open the wave containing the gadget a
second time.

--
http://wave.theWE.net
http://twitter.com/theWE_




On Sun, Dec 6, 2009 at 12:13 AM, Mojo oga...@hotmail.co.uk wrote:
 Browser cookies are definitely a possibility. The only issue I have
 with that is that I wanted to use the Wave datastore because it's
 obviously portable, so it will work if you log in on a different
 machine somewhere else.

 Saving the data server side is also an option, but again I would
 prefer to use Wave's built in capabilities if at all possible.

 I still think there should be a way for Gadgets to store data to the
 datastore without changing the unread status of the wave. Is there??

 I think this issue is probably affecting other Gadgets, not just mine.
 I see other waves rising to the top of my inbox, and when I go to look
 at them nothing appears to have actually changed.

 I'll read up a bit more. I have Sandbox access now, and there might be
 more info on there.

 On Dec 5, 4:43 pm, David Nesting da...@fastolfe.net wrote:
 On Fri, Dec 4, 2009 at 2:58 AM, Mojo oga...@hotmail.co.uk wrote:
  What I need here is a way to save the individual's bookmark setting
  without triggering that updated action for everyone else. I imagine

 Can gadgets write browser cookies?
 What if you saved this state in a server-side data store (wherever your
 gadget is hosted)?

 David

 --

 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-wave-...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-wave-api+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://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 google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.




Re: [Google Wave APIs] Re: State change

2009-12-06 Thread David Nesting
On Sun, Dec 6, 2009 at 12:23 AM, Avital Oliver avi...@thewe.net wrote:

 Gadgets are executed in iframes with variable domains (something like
 *-opensocial.google.com where * can be any number). Cookies are stored
 on a per-domain basis, so you may or may not be able to read the
 cookie you stored once you open the wave containing the gadget a
 second time.


Interesting, so you're saying that the domain may change from one
instantiation of the gadget to another?  I expected that the domain would be
unique, but persistent.

David

--

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-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.