Hello, I was going through this example (TCP client): http://doc.akka.io/docs/akka/current/scala/io-tcp.html
It seems that that article promotes one of Akka anti-patterns, which is passing actor reference by object (to client actor constructor). Is there a way to not make TCP client actor stateful (by being bound to particular actor instance), and instead pass caller actor's ref along with all TCP control messages? I'd like to avoid creating new TCP client instances for each caller instance (and implicitly establishing multiple connections to server). I'd appreciate any info on this. Thanks, M -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
