[Google Wave APIs] Re: State change

2009-12-09 Thread Dan
Understood. Thanks! -- 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

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:/

[Google Wave APIs] Re: State change

2009-12-08 Thread Dan
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 "Googl

Re: [Google Wave APIs] Re: State change

2009-12-06 Thread Avital Oliver
Not only may, it does. Take a look at it. The number at the beginning changes. Not sure based on what, but I've seen it happen many times. I'm guessing the purpose it to make it harder to communicate information between different gadgets (as that might be a breach of privacy). -- http://wave.theWE

Re: [Google Wave APIs] Re: State change

2009-12-06 Thread David Nesting
On Sun, Dec 6, 2009 at 12:23 AM, Avital Oliver 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 op

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

[Google Wave APIs] Re: State change

2009-12-05 Thread Mojo
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