On Friday, July 14, 2017 at 11:55:22 AM UTC+10, James Roper wrote:
>
> We need some form a framing over the TCP connection. A lightweight binary
> protocol could do it, but an easier and probably good enough solution to
> start with is WebSockets with akka-http (to my knowledge akka-http doesn't
I may have some use cases for this, so I've been thinking about what it
could look like. Here are my rough thoughts:
The problem with using Akka remoting is that it's not a guaranteed
transport nor does it provide back pressure - you would have to serialize
the requset packets, and then
No news. We are currently not working on it. You can keep an eye on what is
done in Gearpump.
http://www.gearpump.io/
http://www.marketwired.com/press-release/lightbend-announces-collaboration-bring-low-latency-high-availability-big-data-2099511.htm
On Wed, Apr 6, 2016 at 11:14 PM, César
Hi all,
any news concerning this request?
Cheers
On Thursday, 28 May 2015 11:16:36 UTC+2, Oliver Winks wrote:
>
> Thanks for the info. I'm looking forward to future releases of Akka
> Streams.
> Cheers
>
> On Wednesday, 27 May 2015 22:24:44 UTC+1, Akka Team wrote:
>>
>> Hi Oliver,
>> we do
Thanks for the info. I'm looking forward to future releases of Akka Streams.
Cheers
On Wednesday, 27 May 2015 22:24:44 UTC+1, Akka Team wrote:
Hi Oliver,
we do not (currently) support distributed materialization of streams.
The reason is that it will require implementing redelivery for stream
Hi Oliver,
we do not (currently) support distributed materialization of streams.
The reason is that it will require implementing redelivery for stream
messages and a number of related issues which need to be fixed, which has
not happened yet.
Currently we are focusing on getting the 1.0 out the
Hi,
The way I understand materialisation in Akka Streams is that the
ActorFlowMaterializer will create a number of actors which are used to
process the flows within a stream. Is it possible to control the number and
location of actors that get materialised when running a Flow? I'd like to
be
