On Wed, Oct 21, 2015 at 1:18 AM, Patrik Nordwall
wrote:
> It's not in 2.3
>
Okay -- that's what I thought, from trying to find it in the docs. In
which case, once I'm upgraded to 2.4 (hopefully soonish), I'll upgrade
Requester to use that and see if everything goes smoothly...
--
>>
It's not in 2.3
/Patrik
ons 21 okt. 2015 kl. 01:09 skrev Justin du coeur :
> Okay -- it's on my to-do list. Which is about six miles long, so it may
> be a while, but I'll get to this eventually. The one great annoyance with
> using Requester is the need, under certain circumstances (specifical
Okay -- it's on my to-do list. Which is about six miles long, so it may be
a while, but I'll get to this eventually. The one great annoyance with
using Requester is the need, under certain circumstances (specifically,
when using stash()) to explicitly call its handler. (Which is
automatically de
I'm not sure how many people actually use it - we have not seen too many
questions about it.
Which either means it 'just works' or no-one is using it :-)
If you'd like to give it a spin and provide feedback that'd be awesome!
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 21 October 201
On Mon, Oct 19, 2015 at 3:42 AM, Patrik Nordwall
wrote:
> There is also the Receive Pipeline
> http://doc.akka.io/docs/akka/2.4.0/contrib/receive-pipeline.html
Oh, *neat* -- I've been wanting this for ages. Is this considered
reasonably stable? At a quick look, I suspect Requester should be
r
There is also the Receive Pipeline
http://doc.akka.io/docs/akka/2.4.0/contrib/receive-pipeline.html
/Patrik
mån 19 okt. 2015 kl. 00:33 skrev Konrad Malawski <
konrad.malaw...@typesafe.com>:
> Hi Jan!
>
> Yes, it's definitely one of those
>
> "Do not do this because you will most likely shoot your
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
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])?
