WikiPedia defines 3 basic things that make up actors: * send a finite number of messages to other actors; * create a finite number of new actors; * designate t

WikiPedia defines 3 basic things that make up actors: * send a finite number of messages to other actors; * create a finite number of new actors; * designate the behavior to be used for the next message receives. Now, I'm not saying that xmlrpclib and actors are the same, but one could implement a system that has these properties using xmlrpclib as the basis of transport, and to "designate the behavior to be used for the next message receieves." The way you'd designate is the message you sent, is the handler that gets run. And, if you want to get even more actor like, run xmlrpc servers in their own threads. But, yeah, a real actor system would probably never do this.