Request: Let robots listen to events from other robots

[GoogleCodeExporter]

When a Robot adds another robot to a wavelet, the added one does not
receive a WAVELET_SELF_ADDED-event (occurred with both robots written with
the java-api, don't know if it also happens with the python-api).

Original issue reported on code.google.com by Paul.Staab@gmail.com on 24 Sep 2009 at 9:50

[GoogleCodeExporter]

This is by design - a robot does not see events created by other robots. We 
could 
consider a feature request, if you think there is a valid use case. Can you 
explain 
what you're doing?

Original comment by pamela.fox on 1 Oct 2009 at 3:53

• Changed state: NeedsMoreInfo
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

As wave seems to be very interesting for science, i (and some people from my
workgroup) are currently testing if it is possible to write an molecular 
biological
software-suite for wave.
Such an suite needs many functions for manipulating text, and we think that 
it's best
to create more than one robot offering these for various reasons ("natural 
workflow",
not overwhelming the user with functions, very modular project and therefor 
easier to
maintain and to extend, etc).  
That leads to a point where some robot-robot-communication would be a nice 
thing, so
basically one robot storing some information in the datadocument of the wavelet 
and
some other reacting on it. Therefore i would really be nice if the second robot 
sees
when the first stores the data.
I think that robot-robot-communication will become quite an important issue when
there are more and more complex robots and would therefore really like that to 
be
implemented.

By the way, currently robots often (but not always...) react an
DOCUMENT_CHANGED-events triggert by them self or other robots writing to a 
document.
By what you write, this than seems to be a bug at the moment.

Original comment by Paul.Staab@gmail.com on 3 Oct 2009 at 8:05

[GoogleCodeExporter]

I made a wave-sommelier robot (wave-sommelier@appspot.com) which searches 
wave extensions from the wave-samples-gallery. Its users can choose and add an 
extension to the wave directly from the search results but unfortunately if the 
chosen 
robot is using a gadget, it does not work because of this issue. 

I believe this robot is quite useful for beginners who do not understand how to 
add 
extensions. I hope you to redesign the feature. Or could you tell me the way to 
make 
my robot work correctly?

Original comment by andy...@gmail.com on 28 Nov 2009 at 4:39

[GoogleCodeExporter]

In my opinion, it is a bug. Otherwise, if any event-based communication between 
robots 
is forbidden by design, why allow AddParticipant(robot@...) in the first place? 
A robot 
should see WAVELET_SELF_ADDED when it's added to a wave regardless of who or 
what added 
it.

Original comment by samsonth...@gmail.com on 7 Dec 2009 at 8:06

[GoogleCodeExporter]

I am trying to get two robots to interact:

1. The first (Pushy) adds blips to the wave.
2. The second (Archivey) trims the wave size down to a manageable level.

I'd like these two robots to interact so that when Pushy adds a blip the event 
is 
recorded and Archivey trims down the wave. This doesn't currently happen: see 
this 
wave for the bug report on the wave-api forum:

https://wave.google.com/wave/?
pli=1#restored:wave:googlewave.com!w%252BajhDVE9sA.1

It would be very powerful to allow robots to interact in this way. Perhaps as a 
suggestion the robots could explicitly opt-in to receiving other robot events, 
to 
prevent livelock or similar occurring accidentally.

Original comment by Chris...@gmail.com on 9 Mar 2010 at 9:40

[GoogleCodeExporter]

Original comment by pamela.fox on 14 Mar 2010 at 1:39

• Changed title: Request: Let robots listen to events from other robots
• Changed state: Acknowledged
• Added labels: InternalWave-google.comwjfKpbX6lA

[GoogleCodeExporter]

My use case is that I submit a blip with the Active Robot API, and I want to 
know when I submit it so that I can get the real blip if of the blip that I 
submitted

Original comment by gandalf....@gmail.com on 18 Jul 2010 at 12:33

[GoogleCodeExporter]

Another issue is when you are using something like microwave with robots. 
Because since microwave is in essence a robot, it doesn't notify the robots 
that your are working with of any of your events.

Original comment by gandalf....@gmail.com on 26 Jul 2010 at 4:14

[GoogleCodeExporter]

Update on this? I'd at least expect a fix to be put in place for Data API 
clients.

Original comment by nat.abbo...@gmail.com on 14 Sep 2010 at 8:49