Re: [akka-user] Futures/Actors, Ask/Tell and the (JDBC) blocking problem

2014-06-13 Thread Patrik Nordwall
On Fri, Jun 13, 2014 at 5:25 PM, Richard Rodseth wrote: > Hi Patrik > > I'll try to clarify, though I think this minor code reuse point is > tangential to my main question about the appropriateness of the ask pattern > between service and blocking DAO. > > I suppose I should look at the ask patte

Re: [akka-user] Futures/Actors, Ask/Tell and the (JDBC) blocking problem

2014-06-13 Thread Richard Rodseth
Hi Patrik I'll try to clarify, though I think this minor code reuse point is tangential to my main question about the appropriateness of the ask pattern between service and blocking DAO. I suppose I should look at the ask pattern source code, but presumably it is counting on the recipient to repl

Re: [akka-user] Futures/Actors, Ask/Tell and the (JDBC) blocking problem

2014-06-12 Thread Patrik Nordwall
Hi Richard, On Wed, Jun 11, 2014 at 9:00 PM, Richard Rodseth wrote: > I realize this is well-trodden ground, but it's still a bit confusing for > newcomers. > > Can we agree that the ask pattern is legitimate at the boundary between a > service and repository/DAO? > > It seems to me that it is

[akka-user] Futures/Actors, Ask/Tell and the (JDBC) blocking problem

2014-06-11 Thread Richard Rodseth
I realize this is well-trodden ground, but it's still a bit confusing for newcomers. Can we agree that the ask pattern is legitimate at the boundary between a service and repository/DAO? It seems to me that it is reasonable to want to abstract away the persistence layer in a way that doesn't *ass