This approach does not work with complex data structures. They should be composable, each part separately addressable, other actors should be able to subscribe to the state changes individually. There should be a way to create read-only view for a data and so on.
Approach "just create actor and bunch of accessor messages for wrapped structure" could not scale and adapt for complex structures. , On Friday, August 5, 2016 at 5:45:13 PM UTC+3, Martynas Mickevičius wrote: > > One of the simplest solutions would be to model it as an actor itself. > > A fun challenge would also be to model backgammon board based on a > Conflict Free Replicated Data type. If you solve that, then you could use > Akka > Distributed Data > <http://doc.akka.io/docs/akka/current/scala/distributed-data.html> module. > > On Fri, Aug 5, 2016 at 3:24 PM, scala solist <scala...@gmail.com > <javascript:>> wrote: > > For example, we would like to model the backgammon game with akka actors. >> Both players are actors (either human or AI), there is also an actor that >> rules the board and determines dice rolls for players. They all share the >> single board. What is idiomatic way to have access to the board and to take >> notifications on board position changes? >> >> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
