If you want the most natural way to code your program according to actor model, just use Erlang. It has a zeromq library, hence you can communicate with outside world using zmq.
On Sat, Dec 15, 2012 at 12:27 PM, <[email protected]> wrote: > > hi peeps, > > i would like to ask you for some ideas/hints on an actor-model > design on top of zeromq. zeromq ships with everything i need, > a mailbox, message routing, i don't have to worry about threads etc. > > i think the straightforward way would be to give every actor > one or more sockets for sending and receiving messages, depending > on the used patterns (pub-sub, req-rep). but it seems to be a big > overhead, since the max. number of sockets per context is limited. > on the other hand, i would have to share some sockets and write > a lot of messaging features by myself. so zeromq would be useful > just for the communication between some processes or nodes. > > it's similar to an component based entity system, communication between > entities<->entities, entities<->system and system<->system > should be handled through an event/message bus. Although it's not for game > development, 10k+ entities are possible, which would require > at least more than 10k sockets. > > thank you for your suggestions! > > best regards, > > wil > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
