The user who happens to be viewing the same wave that your Robot is in
isn't "logged in" to the robot's pages in any sense, so it doesn't
make sense to think of the robot handlers as having a "user" at all.
Requests to the robot handler are generated by the wave server to let
your robot interact with the wave itself, not with the users who are
viewing it.

On Sep 13, 7:02 pm, Daniel Faust <[email protected]> wrote:
> I just hit the same problem yesterday. I was trying to associate a
> button press of a FormElement to a user by using the Users Service in
> the OnFormButtonClicked handler.
>
> One thing I'm unable to understand is why the following scenario does
> not work:
>
> I have two tabs open in the browser.
>
> - In one tab I am logged in into my appspot application which is open
> for registrations with google accounts, and the HTTP request handlers
> associate the requests correctly to the user.
>
> - In the other tab I'm logged into Google Wave, and my robot, which is
> the same appspot application as in the other tab to which the
> gmail.com user is logged in, is supposed to associate the users object
> to the gmail.com user who is logged in in the other tab. But to no
> avail, the users object always returns None.
>
> Is this a general restriction? If wavesandbox.com get's transferred to
> google.com on September 30, will that limitation be gone?
>
> Initially I expected that the user object would contain
> "[email protected]", the name, and some id. Since this failed, I
> tried to force the user object to a google account by having the user
> log into the robot via the web interface with his google account. But
> this also failed.
>
> Regards,
> Daniel
--~--~---------~--~----~------------~-------~--~----~
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