Thanks for the response. This is somewhat encouraging. +1 to cookbook and
migration docs.
I'm not up to speed on Flows, so I don't know what the proposed solution
would look like in a route definition.
In the meantime (this is just for a new proof of concept app) I embraced
the Ask in the route de
On Wed, Sep 9, 2015 at 12:27 PM, Patrik Nordwall
wrote:
>
>
> On Wed, Sep 9, 2015 at 12:05 PM, Akka Team
> wrote:
>
>>
>>
>> On Wed, Sep 9, 2015 at 11:59 AM, Patrik Nordwall <
>> patrik.nordw...@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Sep 9, 2015 at 11:17 AM, Akka Team
>>> wrote:
>>>
Hi R
On Wed, Sep 9, 2015 at 12:05 PM, Akka Team wrote:
>
>
> On Wed, Sep 9, 2015 at 11:59 AM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote:
>
>>
>>
>> On Wed, Sep 9, 2015 at 11:17 AM, Akka Team
>> wrote:
>>
>>> Hi Richard,
>>>
>>> There is no easy way currently to do per-request actors (excep
On Wed, Sep 9, 2015 at 11:59 AM, Patrik Nordwall
wrote:
>
>
> On Wed, Sep 9, 2015 at 11:17 AM, Akka Team
> wrote:
>
>> Hi Richard,
>>
>> There is no easy way currently to do per-request actors (except that
>> everything in your handler Flow is kind of a per-request actor), this is
>> something w
On Wed, Sep 9, 2015 at 11:17 AM, Akka Team wrote:
> Hi Richard,
>
> There is no easy way currently to do per-request actors (except that
> everything in your handler Flow is kind of a per-request actor), this is
> something we need to improve. I created an issue:
> https://github.com/akka/akka/is
Hi Richard,
There is no easy way currently to do per-request actors (except that
everything in your handler Flow is kind of a per-request actor), this is
something we need to improve. I created an issue:
https://github.com/akka/akka/issues/18431
-Endre
On Mon, Sep 7, 2015 at 7:23 PM, Richard Rod
I've run into the same problem. How to do per-request actors rather than
ask pattern with Akka Http, and I'm afraid I don't understand how
handlerFlow helps. I've started a separate thread, but if either of you can
elaborate that would be great. The Spray migration page is still marked
TODO.
Thank
Great, thanks for the reply!++nic
On Tuesday, June 16, 2015 at 5:40:55 AM UTC-3, Richard Bradley wrote:
>
> You can see the source code to the net-a-porter Spray example here:
>
> https://github.com/NET-A-PORTER/spray-actor-per-request/blob/master/src/main/scala/com/netaporter/Boot.scala
>
> T
You can see the source code to the net-a-porter Spray example here:
https://github.com/NET-A-PORTER/spray-actor-per-request/blob/master/src/main/scala/com/netaporter/Boot.scala
The startup looks like:
IO(Http) ! Http.Bind(serviceActor, "localhost", port = 38080)
where "serviceActor" is an actor
All right then, except I'm under the impression that to use that pattern we
need to create an application using the `spray.routing.HttpService` class,
and I could not find it in akka-http. Is it available under a different
name?
Thanks,
++nic
On Monday, June 15, 2015 at 3:51:27 PM UTC-3,
The situation is very much the same in Akka HTTP as it was in Spray 1.3.
You should be able to translate the actor-per-request pattern into Akka
with only superficial changes.
If you didn't deal with large (streamed / chunked) requests, everything is
very much the same from Routing on down.
As
11 matches
Mail list logo
