How is it different from xmlrpclib?
http://docs.python.org/library/xmlrpclib.html#example-of-cli...
http://docs.python.org/library/xmlrpclib.html#example-of-cli...
Pykka helps multiple threads (or eventlets if using pykka.gevent) in a single program to communicate in a safe and easy matter without requiring the developer to manage locks and whatnot that he would have if he used plain threads. Under the hood Pykka is just an abstraction on top of threads and queues.
It's not uncommon for actor frameworks, like Akka, to support communication between actors on different computers, but there is currently no support for remote actors in Pykka.
* 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.