I'm facing also this problem with passing a context through the stream. Let say you have a stream like this :
download resource -> back it up -> parse it -> store errors -> process data > -> ... -> persist data -> sink you kinda need some sort of context so that you know that if some latter flows fails it was related to a particular resource from the first Flow and you can log/handle it in Supervision.Decider. I'm using HList for the In&Out Flow types which is basically the context so that instead of gluing flow parts together with many case classes for instance I use a growing HList. But it turned out to be quite a maintenance disaster and it is getting out of control because it lost flexibility. I think that each stream should optionally have something like a Context/GlobalState accessible to all Flows, even if it was a god damn Map[String, Any] because it is impossible to implement it manually for it to be maintainable. -- >>>>>>>>>> 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.
