A big reason why groupBy, splitWhen (and other split* friends) were useful
was the ability to apply different behavior to the bifurcated streams. With
the recent (and, what seems to been a bit sudden) change to SubFlow, I'm
having a difficulty understanding the value of these methods.
It seems like the only thing it offers you, now, is to provide a grouping
for parallelizing the streams, which I'll confess to be somewhat useful for
groupBy, but for the split* family of methods there seems to be little
tenable benefit.
I scanned the gitter backlog for more backstory on why this change
happened. Being acquainted with Roland Kuhn's work, I entirely trust that
it was made thoughtfully and with good reason. Is there anything I can read
to understand more of the motivation for the change? Also, are there any
examples of circumstances in which split{When,After} are useful, now that
bifurcated streams have homogenous processing behavior?
Thanks!
Tim
--
>>>>>>>>>> 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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
