Here's a copy of the message I sent a while back in 2005 regarding  
remote events.... it's still applicable today.

A little background: the event router has its own generator,  
erouterEGID, from which it sends events when listeners are added or  
removed.  This is used for example, by the vision pipeline, to turn  
processing stages on and off when listeners are added/removed.  I  
envision it could also be used by a network interface, so when a  
listener is added on a remote machine, that notification is forwarded  
to the target machine, which then adds a corresponding listener on  
itself, which then forwards any matching events back to the remote  
machine which originally requested it.

So in the PDF below, Aibo1 wants to subscribe to button events on Aibo2.

Also, as discussed at the end of the message, you may want to muck  
around a bit in the wireless/socket class to clean a few things up.   
Feel free to give it a make over ;)

-ethan

----------------------------------------

> Could you send us an overview of the design you had in mind on  
> inter AIBO
> communication. I would very much like to submit it in our group and  
> see if
> we can use this.

Sure!
Basically, the idea I had in mind was that a 'host' field would be  
added to EventBase, and then you would have a separate EventRouter  
instance for each host you wanted to receive events from.  Whenever a  
first listener is added or the last one removed from one of these  
instances, a notification would be sent over wireless to the  
corresponding host that it should start/stop sending the events in  
question.
Behaviors could then check the host field if there is a question as  
to the event's origin, and subscribing to events on other robots  
would be as simple as subscribing to events on the local machine.

I've attached a little PDF that shows how I envision this working out  
in a specific example of one Aibo registering for button events on  
the other: