Hello, We're writing a program that deals with highly parallel network IO, mostly but not only HTTP (using Spray for the HTTP parts).
We needed an internal abstraction for async IO streams. Right now we're using play-iteratee with ByteString. This causes some trouble at the interfaces between this idiom and actors, but we can't use pure actors. Spray and akka-io are lacking an idiom to handle back pressure, compose pipelines (with type information), and a library of common pipeline parts. I understand that a new paradigm called Akka Reactive Streams is in the works to handle just these requirements, and will be part of akka 2.4. Has anything been published publicly about the design of RS (incl. code)? For instance, is it actor-based, or future-based like Iteratees or Observables, or some mix of the two? If actor-based, how does it interact with typed actors, with the existing ack/nack paradigms of akka-io, etc? How does it avoid the overhead of passing a message to successive actors in a pipeline when we really just want to combine a series of pure functions? Etc. I would love to know more. At the very least, we could design our code today in a way that would make it easier to migrate to RS in the future. Thanks! Daniel Armak -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
