Dear hakkers,

we—the Akka committers—are pleased to announce the fourth release candidate for 
Akka Streams & HTTP. The most notable changes since 1.0-RC3 are:

One last big rename (yes, we are truly sorry about that): while the semantics 
had evolved around it, we never adapted the name of the FlowMaterializer—which 
actually is not for Flows but all kinds of Graphs; similarly 
OperationAttributes have no matching “Operation” that they apply to. Hence we 
shortened and simplified
FlowMaterializer to Materializer
ActorFlowMaterializer to ActorMaterializer
OperationAttributes to Attributes
ActorOperationAttributes to ActorAttributes
RunnableFlow to RunnableGraph (for consistency, since this is not a Flow)
optimized some primitive Sources to not create Actors (thanks, Viktor!)
fixed several problematic edge cases around stream and substream cancellation 
and error conditions
added ActorMaterializer.shutdown method to allow external shutdown
added basic framing support for byte streams
made TCP closing mode configurable (i.e. whether to enable half-close)
added a parallel version of foreach and made Sink.ignore materialize to 
Future[Unit]
made multipart/form-data uploads easier
fixed several small kinks in HTTP parsing (cookies, dates, …)
expanded documentation (in particular around HTTPS, websockets and the stream 
testkit)
plus lots of minor additions and improvements

For the full list please refer to the github milestones for Streams 
<https://github.com/akka/akka/issues?q=milestone%3Astreams-1.0-RC4+is%3Aclosed> 
and HTTP 
<https://github.com/akka/akka/issues?q=milestone%3Ahttp-1.0-RC4+is%3Aclosed>.

Our intention (famous last words) is that this should be the last release 
candidate before 1.0, meaning that we would appreciate if you could test the 
provided functionality with real-world use-cases and push it to its limits.

Outlook and Planning: What about Performance?

Version 1.0 is intended to be fully functional but not yet optimized for 
performance. To make it very clear: Spray currently is a lot faster at serving 
HTTP responses than Akka HTTP is. We are aware of this and we know that a lot 
of you are waiting to use it in anger for high-performance applications, but we 
follow a “correctness first” approach. After 1.0 is released we will start 
working on performance benchmarking and optimization, the focus of the 1.1 
release will be on closing the gap to Spray.

Release Statistics

636 files changed, 13061 insertions(+), 6372 deletions(-)

commits added removed
   37    4268    1023 Johannes Rudolph
   25    3309    2078 Endre Sándor Varga
   10     625     425 Mathias
    8     770     101 Martynas Mickevičius
    6     134     446 Viktor Klang
    5     383     179 Roland Kuhn
    4     505     192 Konrad Malawski
    2       7       5 Richard Bradley
    2     490       4 Alexander Golubev
    1      16      22 Martynas Mickevicius
    1       4       4 Philip L. McMahon
    1       8       5 Matthias Lüneberg
    1     169      19 Alek Storm
    1      11       3 Brian Topping
    1      14      14 2beaucoup
    1       1       1 Daniel Wegener
Thanks to Richard, Alexander, Philip, Matthias, Alek, Brian, André and Daniel 
for your contributions!

Happy hakking!


-- 
>>>>>>>>>>      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.

Reply via email to