Bumping this, but I'll add a question about backpressure. For a new TCP project, would you still recommend Akka IO over say Akka + Netty given that Pipelines is deprecated and reactive streams is not ready?
On Fri, Mar 21, 2014 at 8:42 PM, Richard Rodseth <rrods...@gmail.com> wrote: > I've never done any sort of TCP protocol implementation, and am looking at > Akka IO for this purpose. > > I noticed here: > > http://hseeberger.github.io/blog/2013/06/17/introduction-to-akka-i-slash-o/ > > that the "handler" actor calls context.watch() > > // We need to know when the connection dies without sending a > `Tcp.ConnectionClosed` context.watch(connection) > > However, in the Activator tcp-async template, > http://www.typesafe.com/activator/template/tcp-async > > this does not appear to be done. Is this an oversight? > > Also, in both articles, the server/service makes the Bind call. Am I > correct in thinking that if a network collection is lost, Akka IO will > detect this and restart the the server/service actor? > > Finally, do any of the Akka books have a good treatment of TCP, or are > there other good resources besides the two mentioned here? > > Thanks in advance. > > -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
