Re: [akka-user] Akka Http routes in an actor

> On 08 Sep 2015, at 15:46, Richard Rodseth wrote: > > The original inspiration was the Net-a-Porter article and template > https://github.com/NET-A-PORTER/spray-actor-per-request#master > >

Re: [akka-user] Akka Http routes in an actor

The original inspiration was the Net-a-Porter article and template https://github.com/NET-A-PORTER/spray-actor-per-request#master http://techblog.net-a-porter.com/2013/12/ask-tell-and-per-request-actors/ At the time we had a lot of timeout issues. Perhaps these were mostly backpressure-related

[akka-user] Akka Http routes in an actor

I'm trying Akka Http for the first time, coming from Spray. In Spray I have a routing actor which extends HttpService and is passed to HttpBind as shown below. This way routes can create per-request actors as a child of the routing actor. What would be the equivalent in Akka Http? I'm not so

Re: [akka-user] Akka Http routes in an actor

Thanks for the link to that sample. The other problem in doing per-request actors without ask pattern, as in the net-a-porter sample seems to be that Routes are no longer defined as RequestContext => Unit. Any thoughts on that? Are we now required to use Futures (or Flows?) to bridge routing with

Re: [akka-user] Akka Http routes in an actor

> On 07 Sep 2015, at 19:32, Richard Rodseth wrote: > > Maybe just move the bind call into my routing actor, in response to some sort > of Start message ? Yep. Here’s a similar example:

Re: [akka-user] Akka Http routes in an actor

> On 08 Sep 2015, at 07:39, Richard Rodseth wrote: > > Thanks for the link to that sample. > The other problem in doing per-request actors without ask pattern, as in the > net-a-porter sample seems to be that Routes are no longer defined as > RequestContext => Unit. Any