Thanks, Endre. I'm not quite clear on what you're saying - I understand Akka wants to work in peer-to-peer mode, but I don't understand this part:
This does not mean that you cannot use Akka in a Client-Server setup >> though, but you will need to implement your own client-server connection. >> This can be done over pure TCP using akka.io, but you can also make a >> REST endpoint using Spray server and client. >> > Are you saying that Akka *can* work client-server if I implement some class or classes myself and configure Akka to use it/them, or are you saying that I can't use Akka for communication between client and server in this scenario at all (other than Akka I/O, which is not what I'm asking about)? If I need to implement some custom transport for Akka myself, how would I go about that? "Akka custom transport" doesn't produce much in a Google search, are there some other resources? To be clear, I have an existing third party application that uses Akka actor systems for remote communication, so I would prefer a solution that lets me simply configure Akka to use some custom built components rather than having to completely change the interface between client and server. Is this possible? Thanks, Bryn -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
