On Oct 6, 3:55 pm, rick eisenmenger <rick.eisenmen...@gmail.com>
wrote:
> for now I am dragging a wave into another one to examine the link that
> contains the wave id; I hope there are other ways..
I know two ways:
1. Use the URL
* Click on a wave in the Google Wave site, the resulting URL
might look something like this:
https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BP9PIf1t-A
* remove everything except googlewave.com!w%252BP9PIf1t-A
* change the part after the exclamation mark from w%252B to:
w+
* you are done and you wave id is googlewave.com!w+P9PIf1t-A
2. Use a bot
* add blog-...@appspot.com to you wave, it will spit out the
wave id (among other things). Once you get the id you can delete the
bots messages
> How did you manage the authentication against the appserver? (I am
> trying to embed a wave on an application web page on a remote
> server..)
Basically my extension produces some of the html and all of the
javascript of the Hello World example here:
http://code.google.com/intl/sv/apis/wave/embed/guide.html#HelloWorld
All I do with the php code is add the wave id along with the
configuration options.So i did not need to worry about managing the
authentication against the appserver.
/Micke
--~--~---------~--~----~------------~-------~--~----~
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-api@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
-~----------~----~----~----~------~----~------~--~---
