Re: [akka-user] Abridged summary of akka-user@googlegroups.com - 10 updates in 5 topics

Hello Victor, Thank you for your reply. Based on your response I think that I did not express very well what I am seeking. Being able to have the servlet send a message to an actor and vice versa would be perfectly Okay. I am searching for some code that would be a model of how to effect this

Re: [akka-user] Why is aroundReceive protected[akka]?

Hi Jan! Yes, it's definitely one of those  "Do not do this because you will most likely shoot yourself in the foot"? methods, and we believe it's much safer to keep it internal than to make it public, thus encouraging devs to use it (and end up in around-what-hell). We have used it very heavily

[akka-user] Why is aroundReceive protected[akka]?

Hi, looking at akka-streams ActorPublisher recently, I found the approach to implement actor 'base-behavior' using aroundReceive quite elegant and much more natural than partial function chaining. Is there a reason this approach is limited to Akka internals (aroundReceive is protected[akka])?

Re: [akka-user] Re: Behavior of Akka when you sleep in an actor

A dumb question. I was in such a situation recently and have been sleeping threads in Java. I got so much used to it that now I had trouble telling Actor what "heavy work" it should do to stay busy. My solution was File.createTempFile("someRandom", "txt") couple of thousand time (so Actor was

[akka-user] Re: [akka-stream] How to get materialization result in partial flow

The problem with this solution is absence of actorRef during upstream complete. Any ideas how to get it? пятница, 16 октября 2015 г., 15:18:51 UTC+6 пользователь Alexey Romanchuk написал: > > Finally ended with > > ```scala > val managedMySource = FlowGraph.partial(MySource()) { > implicit

[akka-user] Re: No Tests to run for MultiJvm

Thank you friend, that worked well and I was able to run my first multi-ivm test. Here is what my test code looks like. When I run it, I get $ sbt clean

Re: [akka-user] Memory model, messages and remoting

Hi Florian, On Sun, Oct 18, 2015 at 8:00 PM, olf sync wrote: > Thanks √ for your response. > > I use https://github.com/romix/akka-kryo-serialization at the moment. > > I have a lot of actors on System B, which get messages from ONE actor from > system A. They get all the

[akka-user] Re: Proposed major simplification of the Akka Streams FlowGraph APIs

Hi, I like most of the described changes. Here are my personal reservations: 1. I prefer a single method name with many overloads over many method names that say what are the arguments. 2. I think the usage of from in two places (e.g. BidiFlow.fromXYZ and Builder.from(...), might

Re: [akka-user] Re: Proposed major simplification of the Akka Streams FlowGraph APIs

Hi Adam, Thanks for your feedback! Responses inline On 18 Oct 2015 09:36, "Adam" wrote: > > Hi, > > > > I like most of the described changes. > > Here are my personal reservations: > > > > 1. I prefer a single method name with many overloads over many method names that say

Re: [akka-user] Re: Proposed major simplification of the Akka Streams FlowGraph APIs

Ah.. I didn't think of that type erasure issue. Makes sense. RxJava doesn't have a graph DSL as far as I know. I'm guessing you'd have to use Subjects to implement something similar to graphs there, but so far I've never had the need for that. I guess what I usually do with RxJava is more similar

Re: [akka-user] Memory model, messages and remoting

Thanks √ for your response. I use https://github.com/romix/akka-kryo-serialization at the moment. I have a lot of actors on System B, which get messages from ONE actor from system A. They get all the same message and have to keep some information from inside the message inside the actor (but