Dear hakkers,
it has been four weeks since the last milestone was published, so it is high time for the next one. The user-visible changes we have been doing are getting smaller now, cleaning up a few syntax inconsistencies and a few cases where materialized values were picked according to the wrong default, so the good news is that the code base is stabilizing—the bad news is that this is not yet RC1 ;-) (I’m personally blaming ScalaDays, but on the other hand that was the fantastic kind of excuse that one just cannot be angry with.)
The main changes in this milestone are:
fix the bug in bindAndStartHandlingWith, which is has also been renamed to bindAndHandle (for consistency with StreamTcp)
use FlowMaterializer instead of ActorFlowMaterializer arguments where possible
add BidirectionalFlow, which will be used by the upcoming TLS stage (not included yet, the current development state is simply too buggy)
add variants of conditional directive taking only ETag or only Last-Modified value
some more bug fixes, see full list of closed issues
When upgrading from milestone 4 you will notice that we have removed the overloaded variants of Source and Sink factory methods that take a name argument—the syntactic cost (the added parentheses) and complexity was not worth the gain and therefore we replaced this feature by using withAttributes on the returned graphs. Unfortunately this requires some mechanical adaptations of your source code along these lines:
1.0-M4:
val sink: Sink[Int, Future[Int]] = Sink.head[Int]()
val firstPair: Future[(Int, Int)] = pairs.runWith(Sink.head())1.0-M5:
val sink: Sink[Int, Future[Int]] = Sink.head[Int]
val firstPair: Future[(Int, Int)] = pairs.runWith(Sink.head)The activator templates have also been updated:
We’d like to thank all of you for testing and for providing feedback on our progress. In particular we thank Daniel Wegener, Wojciech Jurczyk, and Richard Bradley for their patches.
Happy hakking!
Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Reactive apps on the JVM.
twitter: @rolandkuhn
could we split akka-stream and akka-http as two separate release cycles?
在 2015年3月28日星期六 UTC+8上午5:05:12,rkuhn写道:
--
>>>>>>>>>> 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+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.