Hi! I'm struggling to build something like conveyor system for file processing. The main idea is to have combinable conveyor stages which can operate on ByteStrings streamed throught them and this use case seems to be a perfect fit for reactive streams. However the conveyor stages also need to extract some meta information from Bytestrings passing through them and somehow send it down to other parts of the system but I'm not sure what is the best/most idiomatic way to do it in the world of reactive streams. My current solution is to have stages defined as *class ConveyorStage extends Actor with ActorPublisher[Either[Bytestring, MetaInfo]] with ActorSubscriber* and then split ByteStrings and MetaInfo to different sinks in the end but it doesn't look conceptually right. I think that the most idiomatic way would be to have a Processor which is part of two separate streams at the same time and have an ability to emit to any of them according to it's inner logic but I can't find any references in documentation how to use the same "singleton" actor processor in different materialized streams. Is this the right direction or am I overengineering it? I'm quite new to all this reactive stuff and there are high chances that I completely misunderstood the concept. So any advice/clarification/guideline would be greatly appreciated. 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 [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.
