On Fri, Nov 27, 2015 at 7:15 AM, Leon Ma wrote:
> Is it available in 2.0-M1 now?
>
2.0-M1 is basically 1.1 so you should update anyway (more likely to M2
which we will release soon). The feature is not yet available as it
requires many internal changes that are 90% done now. You won't see the
in
Is it available in 2.0-M1 now?
在 2015年11月26日星期四 UTC-8上午1:17:46，Akka Team写道：
>
> Hi Leon,
>
> > Just worry about the cost of the materialization, if the stream is
> pretty complex which involves a lot of actor creations.
>
> Yes, this is one reason why Akka Http is not as fast yet as it can be.
>
Hi Leon,
> Just worry about the cost of the materialization, if the stream is pretty
complex which involves a lot of actor creations.
Yes, this is one reason why Akka Http is not as fast yet as it can be.
Luckily, this is exactly what we are working on, as 2.0 will allow fusing
graphs into one ac
Just worry about the cost of the materialization, if the stream is pretty
complex which involves a lot of actor creations.
If it's just "per connection" rather than "per request", then I think it's
not a big deal. (Assuming the connection object is reusable across requests)
Leon
在 2015年11月25日
Ok, then the answer is that one stream will be materialized for each
incoming connection sharing the lifecycle of the connection.
Why does this matter btw?
-Endre
On Wed, Nov 25, 2015 at 9:02 AM, Leon Ma wrote:
> Hi, Endre
>
> The code snippet is copied from akka.http.scaladsl.Http.scala
>
>
>
Hi, Endre
The code snippet is copied from akka.http.scaladsl.Http.scala
在 2015年11月24日星期二 UTC-8上午6:14:30，Akka Team写道：
>
> Hi Leon,
>
> On Tue, Nov 24, 2015 at 2:38 PM, Leon Ma >
> wrote:
>
>> Hi,
>>
>> Checking below code:
>>
>> bind(interface, port, settings, httpsContext, log)
>> .m
Hi Leon,
On Tue, Nov 24, 2015 at 2:38 PM, Leon Ma wrote:
> Hi,
>
> Checking below code:
>
> bind(interface, port, settings, httpsContext, log)
> .mapAsyncUnordered(settings.maxConnections) { connection ⇒
> handleOneConnection(connection).recoverWith {
> // Ignore inco
Hi,
Checking below code:
bind(interface, port, settings, httpsContext, log)
.mapAsyncUnordered(settings.maxConnections) { connection ⇒
handleOneConnection(connection).recoverWith {
// Ignore incoming errors from the connection as they will cancel
the binding.
