> 9 feb 2015 kl. 21:57 skrev Ivan Topolnjak <ivant...@gmail.com>: > > Hello there! > > It's really exciting to see where the Akka Streams & HTTP projects are > heading, congrats to the team and to all contributors for such a great gift > to the community. Now, I know you get asked for WebSockets support a lot, but > this announcement made me wonder: Is the first release of akka-http going to > include WebSockets support?.... I always thought that there was going to be a > first release that was feature wise equal to Spray and then afterwards > another release with WebSockets support, but the fact that it is the next > task on the HTTP front seems quite interesting! Hope you have good news on > this matter :D.
As always, plans are intentions, not facts ;-) We are nearing feature parity with Spray, but we won’t make sure to hit that line exactly—we have already improved upon Spray in some areas—we’ll release what we have when we have it. Concerning WebSockets it turns out that their implementation may or may not require the introduction of a new DSL element for Streams, so figure that out is the next thing that needs doing before we can finalize the Streams DSL. Regards, Roland > > On Fri Feb 06 2015 at 4:05:23 PM Roland Kuhn <goo...@rkuhn.info > <mailto:goo...@rkuhn.info>> wrote: > And in the rush of course I forgot one thing: Thanks a lot to Greg Beech for > adding the “Age” and “Expires” headers to our HTTP model! > >> 6 feb 2015 kl. 15:56 skrev Roland Kuhn <goo...@rkuhn.info >> <mailto:goo...@rkuhn.info>>: >> > >> Dear hakkers, >> >> it has been over a month, so we figured that another milestone of our >> Streams & HTTP projects is in order. The Christmas break was a bit longer on >> the HTTP side (i.e. not so many changes there), so most of the work went >> into streams: >> >> consistently use the word “failure” instead of “error” in the API (see here >> <http://www.reactivemanifesto.org/glossary#Failure> for the definitions) >> rename all materializing actions such that they start with “run” (e.g. >> “runForeach”) to distinguish them from non-materializing ones >> rename ActorBasedFlowMaterializer to ActorFlowMaterializer (which now uses >> ActorFlowMaterializerSettings) >> make use of DeadLetterSuppression to avoid pointless warning messages, also >> sanitize failure logging in stream stages to avoid duplicates >> fix a few issues with StreamTcp concerning connection termination >> last but certainly not least: translate the Scala reference documentation to >> Java (cookbook still missing at this point) >> >> What next? >> >> When starting to work on the integration for our SslTlsStage we encountered >> some difficulties with the current internal design—in fact this reminded us >> that we had not yet implemented some of the semantics of reusing flow >> topology blueprints within larger graphs. This triggered a rewrite of the >> internal representation of FlowGraph that is currently under way. While >> doing this we discovered another difficulty related to extracting >> materialized values (like the local socket address for a server binding, or >> a completion future for a Sink) when reusing the same blueprint multiple >> times within a larger graph, and the solution for this needs an API change: >> version 1.0-M4 (to be released in two weeks time) will introduce one more >> type parameter for all graph elements that materialize to a value, namely >> the type of that value. Composition operators and graph constructors (like >> Source(), FlowGraph() and Sink()) will require explicit functions that >> describe how these materialized values are composed, and overall >> materialization of a RunnableFlow will then yield only the overall >> (composed) value instead of a MaterializedMap. This should be safer and more >> intuitive to use than what we have currently. After this change we plan on >> keeping the API stable (with the caveat that future enlightenment might >> reveal flaws yet unknown). >> >> On the HTTP front the next task is to start the implementation of >> WebSockets, and once TLS is available on the Streams layer we will hook that >> up into HTTP as well. >> >> All your feedback (on this list and on github) has been very helpful in >> pushing Akka Streams & HTTP forward, please stay awesome :-) >> >> Regards, >> >> Dr. Roland Kuhn >> Akka Tech Lead >> Typesafe <http://typesafe.com/> – Reactive apps on the JVM. >> twitter: @rolandkuhn >> <http://twitter.com/#!/rolandkuhn> >> >> >> -- > >> >>>>>>>>>> Read the docs: http://akka.io/docs/ <http://akka.io/docs/> >> >>>>>>>>>> Check the FAQ: >> >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> <http://doc.akka.io/docs/akka/current/additional/faq.html> >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> >>>>>>>>>> <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 >> <mailto:akka-user+unsubscr...@googlegroups.com>. >> To post to this group, send email to akka-user@googlegroups.com >> <mailto:akka-user@googlegroups.com>. >> Visit this group at http://groups.google.com/group/akka-user >> <http://groups.google.com/group/akka-user>. > >> >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > Dr. Roland Kuhn > Akka Tech Lead > Typesafe <http://typesafe.com/> – Reactive apps on the JVM. > twitter: @rolandkuhn > <http://twitter.com/#!/rolandkuhn> > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ <http://akka.io/docs/> > >>>>>>>>>> Check the FAQ: > >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> <http://doc.akka.io/docs/akka/current/additional/faq.html> > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > >>>>>>>>>> <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 > <mailto:akka-user+unsubscr...@googlegroups.com>. > To post to this group, send email to akka-user@googlegroups.com > <mailto:akka-user@googlegroups.com>. > Visit this group at http://groups.google.com/group/akka-user > <http://groups.google.com/group/akka-user>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Akka Developer List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to akka-dev+unsubscr...@googlegroups.com > <mailto:akka-dev+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. Dr. Roland Kuhn Akka Tech Lead Typesafe <http://typesafe.com/> – Reactive apps on the JVM. twitter: @rolandkuhn <http://twitter.com/#!/rolandkuhn> -- >>>>>>>>>> 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.
