strange behavior to add a participant named foo@gmail.com

[GoogleCodeExporter]

The code below adds a participant named 'foo@googlewave.com', but the new wave 
is not in the 
foo's inbox.

wavelet = active_robot.fetch_wavelet(wave_id, wavelet_id)
wavelet.participants.add('foo@gmail.com')
active_robot.submit(wavelet)

Original issue reported on code.google.com by andy...@gmail.com on 3 Apr 2010 at 3:11

[GoogleCodeExporter]

Original comment by pamela.fox on 4 Apr 2010 at 6:15

• Added labels: ApiType-Robots, Type-Defect

[GoogleCodeExporter]

Why aren't you adding them using the @googlewave.com address?

The Wave client does attempt to convert gmail addresses to Google Wave 
addresses in 
the participant adder, but I don't believe the server is designed to.

Original comment by pamela.fox on 8 Apr 2010 at 12:09

• Changed state: NeedsMoreInfo

[GoogleCodeExporter]

I made a web service which opens a new wave with a participant whose address is 
given by a user of the web 
service. When the user inputs 'foo@gmail.com' at first, the active robot api 
looks work well but the new wave will 
not appear in the user's inbox. Then the user adds 'foo@googlewave.com' to the 
wave, it appears in the user's 
inbox with two 'foo@googlewave.com.' It's a quite confusing behavior for robot 
developers.

I know, developers can convert from '@gmail.com' to '@googlewave.com' by 
themselves but it does not seem to be a 
good idea for me.

What I want for gwave to do is not that the robot api converts users' domain 
automatically, but that its api and its 
client behave in same way. In other words, I wish the client shows a new wave 
in inbox or stops converting a 
participant's domain if participants is added by the active api.

Original comment by andy...@gmail.com on 8 Apr 2010 at 4:44