Good job guys
On 3 April 2016 at 20:55, paweł kamiński wrote:
> +1
>
> On Friday, 1 April 2016 18:38:32 UTC+2, drewhk wrote:
>>
>> Yay!
>>
>> On Fri, Apr 1, 2016 at 6:37 PM, Konrad Malawski wrote:
>>
>>> ANNOUNCE: Akka 2.4.3 Released
>>>
>>> Dear hakkers,
yeah, I ve just seen it was released. thanks guys - just in time ;]
On Friday, 1 April 2016 11:48:39 UTC+2, drewhk wrote:
>
> Or wait until 2.4.3 and use the KillSwitch feature, as it was mentioned
> before:
>
> 1. unbind server
> 2. wait until grace period, then trigger KillSwitch.shutdown or
+1
On Friday, 1 April 2016 18:38:32 UTC+2, drewhk wrote:
>
> Yay!
>
> On Fri, Apr 1, 2016 at 6:37 PM, Konrad Malawski > wrote:
>
>> ANNOUNCE: Akka 2.4.3 Released
>>
>> Dear hakkers,
>>
>> we—the Akka committers—are proud to announce the third patch release of
>> Akka 2.4.
>>
I'll open a bug. Thanks for the tip about the async.
I'm using a flow here because its a model for the much more complex flow
I'll be using in my actual project.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
Hello,
I have got a piece of code (see bellow) which spawns a server that echoes
every stream of ByteString it receives from port 6001.
The example also defines a client that connects to the server and sends a
stream of ByteString containing a list of characters from letter 'a' to 'z'.
The exception might be a bug. Please open an issue in
https://github.com/akka/reactive-kafka
You should use mapAsync for the commits. Otherwise you loose the
backpressure. commit returns a Future.
You don't need to use a graph for that simple flow, see the examples.
/Patrik
sön 3 apr. 2016 kl.
This question was not answered at
https://stackoverflow.com/questions/36348020/kafka-message-to-websocket so
I ask here.
Thanks
Vish
===
I am trying to write a Kafka consumer to websocket flow using
reactive-kafka, akka-http and akka-stream.
val publisherActor =