Encouraged by other team members, I've re-factored my blocking,
*Await#result* (returning type T) calls with *Future[T]*.
Here's an example for readers who aren't familiar:
scala> import scala.concurrent.{Future, Await}
import scala.concurrent.{Future, Await}
scala> import scala.concurrent.Ex
Thank you everybody,
As I didn't find any help about single node cluster sharding
integration tests, I
published my test environment code. Please let me know if I
did anything wrong.
Regards,
Amir
On 09/02/2015 01:04 AM, Justin du coeur
It is already 2.4.0-RC1. It is supposed to reduce latency. You can read
more about it in the pull request https://github.com/akka/akka/pull/18113
On Thu, Sep 3, 2015 at 5:16 PM, Guido Medina wrote:
> Hi Patrik,
>
> That's great news, does the TCP no delay affect remote performance in
> anyway? I
Hi Patrik,
That's great news, does the TCP no delay affect remote performance in
anyway? If so is that change reflected at 2.4-RC1 or is it coming in the
next 2.4 release?
Best regards,
Guido.
On Thursday, September 3, 2015 at 2:04:20 PM UTC+1, Patrik Nordwall wrote:
>
> Dear hAkkers,
>
>
> W
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability
of Akka 2.3.13. This is the 13th maintenance release of the 2.3 branch.
This release contains a few important fixes:
-
backport ClusterClient failure detection improvement
-
fix AbstractFSM.on
чт, 3 сент. 2015 г. в 11:38, Patrik Nordwall :
> On Fri, Aug 21, 2015 at 5:46 PM, Alexey Shuksto wrote:
>
>> Well, I was able to achieve needed behavior with following flow scheme:
>>
>> Flow() { implicit builder ⇒
>> val promises = builder add Source(() ⇒ Iterator continually Promise[O]())
>>
Hi Robert,
The problem with old Java domain objects IMHO is how to properly guard
their state, for example, you might think of solutions like Loading caches
using Guava or any other caching framework but that still doesn't free you
from mutability problems, caching is one of the hardest problem
By the way, I created an issue for this
https://github.com/akka/akka/issues/18392
On Thu, Sep 3, 2015 at 11:09 AM, Patrik Nordwall
wrote:
>
>
> On Mon, Aug 31, 2015 at 12:13 PM, Leon Ma wrote:
>
>> Hi,
>>
>> I have below Actor which can return a chunked response:
>>
>>
>> class DemoActor extend
I don't think there are any metrics yet. There are some tickets related to
this:
https://github.com/akka/akka/issues/17095
https://github.com/akka/akka/issues/16858
/Patrik
On Sat, Aug 29, 2015 at 3:15 PM, wrote:
> Can I get any metrics from Http.get(system).singleRequest(...) ?
> Just would li
On Mon, Aug 31, 2015 at 12:13 PM, Leon Ma wrote:
> Hi,
>
> I have below Actor which can return a chunked response:
>
>
> class DemoActor extends Actor {
>
> override def receive: Receive = {
> case req: HttpRequest =>
>
> val source = Source(List(Chunk("Hello"), Chunk("World"), LastCh
I see. Thanks a lot!
On Thu, 3 Sep 2015 10:33:42 +0200
Konrad Malawski wrote:
> Hello Eax,
> Akka Http can be seen as the "Spray 2.0".
>
> It's been developed together by us and Mathias and Johannes (the
> original Spray team), if that clears up the relationship of those two.
>
> Once we get p
On Fri, Aug 21, 2015 at 5:46 PM, Alexey Shuksto wrote:
> Well, I was able to achieve needed behavior with following flow scheme:
>
> Flow() { implicit builder ⇒
> val promises = builder add Source(() ⇒ Iterator continually Promise[O]())
>
> val fan = builder add Broadcast[Promise[O]](2)
> v
Hello Eax,
Akka Http can be seen as the "Spray 2.0".
It's been developed together by us and Mathias and Johannes (the original Spray
team), if that clears up the relationship of those two.
Once we get performance nailed with Akka Http we will start recommending to
migrate to Akka Http from Spra
The supervision decider is used for specifying if the stream is supposed to
be completed with failure (stop) or discard the exception and continue
anyway (resume, restart). What you describe is that you want to convert the
exceptions to ordinary stream elements. That is not done with a decider.
You
Hello.
I heard different opinions regarding future of Spray. One people say
that Akka Http is a new Spray and Spray will not evolve further. Other
say that Spray will definitely be developed as separated project.
Who is right?
--
Best regards,
Eax Melanhovich
http://eax.me/
--
>>
15 matches
Mail list logo
