I just have noticed master hasn't anymore akka-stream subproject. Does it
mean akka (and Scala in whole) reactive streaming is preparing for the next
reincarnation? :)
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Uhm, I don’t think it ever had streams in it, hm! :-)
The streams are in active development and are located in the release-2.3-dev
branch.
Slightly hidden we know, on the other hand, it’s very aggressively changing, so
that may be a good thing…
Anyhow, you’re free to give it a spin! Feedback is
Sorry, my mistake, I mean There are *no* akka-stream I haven't found
a way to edit the subject.
--
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
No worries, https://github.com/akka/akka/tree/release-2.3-dev/akka-stream
Happy hakking :-)
--
Konrad 'ktoso' Malawski
hAkker @ typesafe
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Yes, perhaps I should explain our current workflow with these branches
actually:
master will eventually become akka 2.4.x
release-2.3 will eventually become akka 2.3.4 (and 2.3.5 if it’s needed
etc).
release-2.3-dev is used only for streams development. It is separate to
keep iterating /
Howdy All,
I've been reading lots of threads on the Akka User mailing list and pull
requests and blog posts within the community but I am confused about what
currently are the best practices for:
1. Distributed and Resilient Pub-Sub within Akka
It seems to me that a resilient pub-sub is a
