illSwitch.shutdown or abort
> 3. shut down ActorSystem
>
> -Endre
>
> On Fri, Apr 1, 2016 at 11:33 AM, Viktor Klang <viktor...@gmail.com
> > wrote:
>
>> Call 'shutdown' on the ActorSystem? Or only the Materializer?
>>
>> On Fri, Apr 1, 2016 at 11:29 AM, paweł
+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.
>>
ination" or something with a
> code path attached to it?
>
> On Thu, Mar 31, 2016 at 11:53 PM, paweł kamiński <kam...@gmail.com
> > wrote:
>
>> dont take it personally, there is a lot to process and sometimes it is
>> easy to overlook the most important part
I thought bold is new black, coming back with a bang...
ok, your explanation makes kind of sense ;] all I expected was a shutdown
method with timeout.
and yeah a section with examples would be nice and I can write one once I
understand how it works ;]
I understand that I need to hold each
hi, I have a simple http service that binds to a given port and starts
accepting IncomingConnection.
the server is created by actor on its preStart callback and stopped on
postStop.
everything works fine until I try to kill the actor and force http-server
to stop.
public void start() {
ook into it soon!
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> <http://akka.io>Akka <http://akka.io> @ Lightbend
> <http://www.google.com/url?q=http%3A%2F%2Ftypesafe.com=D=1=AFQjCNFC6SplTJxAP7AExZl1lClfJ-tq6w>
> <http://lightbend.com>
>
> On 8
:02 UTC+1, paweł kamiński wrote:
>
> thanks, for all help.
>
> it is running for ever as I am testing concepts of updating a remote
> client asynchronously, in real time Updater will get updates from other
> actors and yes I will add supervision strategies.
> Im running thi
the flow.
On Tuesday, 8 March 2016 23:33:38 UTC+1, Rafał Krzewski wrote:
>
> W dniu wtorek, 8 marca 2016 23:10:38 UTC+1 użytkownik paweł kamiński
> napisał:
>>
>> but this is impossible to change concurrently as I log it and then pass
>> to Pattern#ask. I just wonder wh
ncurrently by
> different threads, but since updater is a local variable in the closure
> passed to mapAsync, this really shouldn't been happening... Weird.
>
> I guess that's all I can say without digging in with a debugger :) Good
> luck!
> Rafał
>
> W dniu wtorek, 8 marca 2016 18:
party components such as actors.
> this is a bit confusing as there is a ActorPublisher that would be good
> fit here if only Flow had a construct like Source.actorPublisher() / Sink.
> actorRef(). this way we could pass Props of publisher which would
> transform incoming messages into
y something we'll do next up,
> please keep the feedback coming, thanks!
>
>
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> <http://akka.io>Akka <http://akka.io> @ Lightbend <http://typesafe.com>
> <http://lightbend.com>
>
> On 8 March 2016 at 17:14
I try to force my http server (using only http-core) to respond with
headers.
I get from request Accept header
String mime = request.getHeader(Accept.class)
.map(HttpHeader::value)
.orElse("application/json");
but then it is not clear to me how to create custom Content-Type
like Source.actorPublisher() / Sink.
actorRef(). this way we could pass Props of publisher which would transform
incoming messages into something else.
On Monday, 7 March 2016 11:28:03 UTC+1, paweł kamiński wrote:
>
> yep, i'm now thinking about duplex flow so I can push incoming me
10:43:26 UTC+1, Rafał Krzewski wrote:
>
> W dniu poniedziałek, 7 marca 2016 10:08:23 UTC+1 użytkownik paweł kamiński
> napisał:
>
>> thanks for response.
>>
>> well ask pattern is a way to go but I thought I could avoid it and use
>> only flow's connection
Object-akka.util.Timeout-
>
>
> W dniu niedziela, 6 marca 2016 23:25:07 UTC+1 użytkownik paweł kamiński
> napisał:
>>
>> hi,
>> I have a simple HTTP service that accepts connections and keeps them
>> alive.
>> Once client sends something I look-up actor
hi,
I have a simple HTTP service that accepts connections and keeps them alive.
Once client sends something I look-up actorRef (WORKER) based on path/query
of request and I would like to wait for response from such actor so I can
respond back to client.
this is server to server communication
I guess the answer can be found on the same page I referred.
1. final Flow<Message, Message, BoxedUnit> flow = stack.atop(stack.
reversed()).join(pingpong);
I need to close BidiFlow from one end to get Flow of the other end
On Wednesday, 16 September 2015 23:09:46 UTC+2, paweł ka
ngpong);
>>
>> I need to close BidiFlow from one end to get Flow of the other end
>>
>> On Wednesday, 16 September 2015 23:09:46 UTC+2, paweł kamiński wrote:
>>>
>>> hi,
>>>
>>> I folowed
>>> http://doc.akka.io/docs/akka-stream-
thanks for detailed answer, and yes now I understand it, it just was't
explained in details in docs and I got impression it should be doable and
useful :)
On Friday, 18 September 2015 13:07:40 UTC+2, drewhk wrote:
>
> Hi Pawel,
>
> On Fri, Sep 18, 2015 at 12:19 PM, paweł k
hi,
I
folowed
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/java/stream-graphs.html#Bidirectional_Flows
and its section describing BidiFlow but my brain has just fried when I
tried to figure out how to expose left side of such BidiFlow as Flow.
in other words how to hide
nputs.map { in => sourceFor(in) }.flatten(FlattenStrategy.concat)
>
> I have written some TCP examples for an older ML thread, they might help
> to give you some inspiration:
> https://gist.github.com/drewhk/25bf7472db04b5699b80
>
> (try to run them to see what they do)
>
hi,
I have a problem with defining a flow that reacts to incoming data and
producing dynamic response.
lets say I have a tcp server
Tcp
.get(system)
.bind(host, port)
.to(foreach(con -> {
con.handleWith(handlerFlow, materializer);
}))
`.ObjectmapMaterializedValue(m - m)` to
convert the type.
Johannes
On Tue, Aug 25, 2015 at 11:19 PM, paweł kamiński kam...@gmail.com
javascript: wrote:
OK I give up again :)
so if I have
SourceInteger, BoxedUnit source = producer.produce(10, 100);
and encoder
the Source provides), you can also use
HttpEntityies.create(contentType, length, data)
to create a (non-chunked) streamed default entity.
HTH
Johannes
On Monday, August 10, 2015 at 10:38:40 PM UTC+2, paweł kamiński wrote:
hi,
probably again I ve overlooked it in documentation but I cannot
provides), you can also use
HttpEntityies.create(contentType, length, data)
to create a (non-chunked) streamed default entity.
HTH
Johannes
On Monday, August 10, 2015 at 10:38:40 PM UTC+2, paweł kamiński wrote:
hi,
probably again I ve overlooked it in documentation but I cannot find
a iterator based Source to emit the 100 elements instead
of sending them via the ActorPublisher actor you would have backpressure
all the way.
What is it that you are trying to build?
On Thu, Aug 6, 2015 at 9:42 PM, paweł kamiński kam...@gmail.com
javascript: wrote:
thanks for your
hi,
I have simple actor producer based
on
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/java/stream-integrations.html#ActorPublisher
public class MessageProducer extends AbstractActorPublisherMessage
{
private final static Logger logger =
27 matches
Mail list logo