Events already have LoadBuffer/SaveBuffer serialization functions,  
and with the EventTranslator class to allow polymorphic operation,  
the main holdup is the networking.  The problem there is that we  
don't currently have the ability to "pull off" an incoming  
connection, so at the moment we can't have more than one connection  
per service.  This means that if you have more than two (say 'N')  
Aibos that you want to be fully connected to each other, currently  
you'd have to pre-allocate the N-1 clients and servers on each aibo,  
each server assigned a different port number, and somehow map each  
listener to a different server port on each other Aibo.  There are  
ways to do this, but it would be much cleaner just to fix the main  
problem so that each client can connect to the same port number, and  
each Aibo creates new servers as needed.

So I think the best way to solve this is to add multi-connection  
support to the Wireless, so that when a new connection comes in to a  
server port, it gets pulled off to a different port so that the  
server port is still available for new connections.  A new callback  
form would have to be added so the port number (and/or a void*  
argument for client-specific data, which is also currently lacking)  
could be passed whenever new data arrives on the port.  Could also  
add callbacks for connection open/close, which would be nice.

I hate to subject you to the mess that is the Aibo's networking API  
(it Sony's own custom design), but I'm happy to give you what  
assistance I can.  I think solving this basic networking issue will  
make life a lot easier for a lot of people, I've been wanting to get  
around to this for a long time, but I don't think I would get around  
to it myself any time soon.

-ethan