Hello hakkers!
I have check ActorConsumer trait in 0.3-SNAPSHOT and 0.3 release and API
looks strange for me. In then one hand we have FlowMaterializer that manage
how flow will be materialized and in then another RequestStrategy from
ActorConsumer.
It looks like both of them are manage ways how messages will flow in flow.
Here it is the short example:
val source = as.actorOf(Props[ExternalAPI])
val saver = as.actorOf(Props[SlowSaver])
val materializer = FlowMaterializer(MaterializerSettings(
initialInputBufferSize = 8,
maximumInputBufferSize = 8
))
Flow(ActorProducer[Int](source))
.produceTo(materializer, ActorConsumer[Int](saver))
In this example settings defined by materializer does not used at all. Am I
right? If yes maybe we should try to find way to merge them together?
Thanks!
p.s. Sorry if it is wrong list for this question.
--
>>>>>>>>>> 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.
