Re: [akka-user] How to create an Actor System Integration test with TestProbes?

Thank you, that was just what I needed. On Monday, October 3, 2016 at 9:55:28 AM UTC-4, loe...@posteo.de wrote: > > The following might help: > https://github.com/hseeberger/reactive-flows/blob/master/src/main/scala/de/heikoseeberger/reactiveflows/FlowFacade.scala#L72 > > > On 3 Oct 2016, at

Re: [akka-user] the meaning of Actor.receive and context.become

Hi Bert, There is no public access to the current behaviour of the actor in the API so this you would have to implement yourself. -- Johan Akka Team On Fri, Sep 30, 2016 at 3:07 AM, Bert Robben wrote: > > I'm puzzled by the meaning of Actor.receive() and

[akka-user] Re: Convert CompletionStage Type

I looked for that but CompletionStage doesn't have a map method. At least not in the Java8 version of java.util.concurrent.CompletionStage. On Monday, October 3, 2016 at 10:41:23 AM UTC-7, Josep Prat wrote: > > It's not very stylish, but you can call map on the CompletionStage doing a > cast to

Re: [akka-user] How to Increase (AKKA-HTTP Client) singleRequest response chuck size

Hi Tal, The settings you reference are only about the maximum sizes before the client fails rather than returning the response, it cannot affect how large chunks the server returns. Additionally the the OS on the sending side, network devices between the client and server and the receiving client

Re: [akka-user] Akka scheduler

Hi Jose, There are to few details in the provided code sample to say for sure, it depends on what your Routing actor does when handleMessage returns and also how your SpringExtension integration works. -- Johan Akka Team On Tue, Sep 13, 2016 at 4:58 PM, José Diaz wrote:

[akka-user] Convert CompletionStage Type

I am creating a directive for Akka HTTP using the javadsl that performs an ask on an actor and then returns the resulting object in a type-friendly way that other directives and route handlers can process easily. For example: public CompletionStage askActor(String actorPath, Object message,

[akka-user] Re: thread-pool-executor with fixed-pool-size clarification

Also, I believe that it should be consistent, I think Java fixed thread pool factories will give you a thread pool that expire the threads after 1 minute being idle, should be the same *-consistency-* for Akka? On Monday, October 3, 2016 at 4:20:01 PM UTC+1, Guido Medina wrote: > > Look and

Re: [akka-user] Ask or Tell ?

You should also think about what happens if you don't get any replies. In the end the actor should probably be stopped to avoid resource "leak". On Mon, Oct 3, 2016 at 9:14 AM, Roland Kuhn wrote: > Yes, almost: it should be context.actorOf, not system.actorOf. > > Regards,

Re: [akka-user] Ask or Tell ?

Yes, sorry, state is good but per actor, so that I should create one actor instance each time I would like to combine the two CSV. So, given that actor should/can have states and that *tell* is the preferred approach. I should have something like that : class Combiner(subject:Subject,

Re: [akka-user] Ask or Tell ?

> 3 okt. 2016 kl. 14:30 skrev gervais.b : > > Hello, > > I'm fairly new with Akka (and maybe the whole question below is polluted by > my synchronous background). In my app, I have to parse 2 CSV available as > HTTP, I plan to access them from one actor that accept two

[akka-user] Ask or Tell ?

Hello, I'm fairly new with Akka (and maybe the whole question below is polluted by my synchronous background). In my app, I have to parse 2 CSV available as HTTP, I plan to access them from one actor that accept two messages (one per csv). But I should add another HTTP resources next week. So