I'm not qualified to address your questions directly but I find a good
place to start when looking for akka patterns is the typesafe activator.
Here http://typesafe.com/activator/template/akka-clustering is one on a
clustered subpub. might be interesting for you.
On Wednesday, August 13, 2014
(and not have regexes for dates and
custom `At` types) but could re-use existing `Instant`s etc.
Keep at it, good luck! :-)
On Mon, Aug 4, 2014 at 5:59 PM, Greg Flanagan vent...@gmail.com
javascript: wrote:
Hey Odd,
This looks promising. Thanks for passing along.
Greg
On Sunday, August 3
akka-camel.
On Fri, Jul 25, 2014 at 5:46 PM, Greg Flanagan vent...@gmail.com
javascript: wrote:
Endre,
Seems reasonable to keep the scheduler light weight and performant. My
plans were to build something around it. Thanks.
Greg
On Friday, July 25, 2014 7:40:39 AM UTC-7, Akka Team
to be solved… :-)
— k
On 28 July 2014 at 04:05:55, Greg Flanagan (vent...@gmail.com
javascript:) wrote:
I'm building a reporting backend where users can schedule a report to be
run weeks / months in advanced. I've used Quartz in the past for this kind
of things but my use case isn't
I'm building a reporting backend where users can schedule a report to be
run weeks / months in advanced. I've used Quartz in the past for this kind
of things but my use case isn't that complex and I think I can get away
with just using the akka scheduler (plus I just don't like Quartz and would
Endre,
Seems reasonable to keep the scheduler light weight and performant. My
plans were to build something around it. Thanks.
Greg
On Friday, July 25, 2014 7:40:39 AM UTC-7, Akka Team wrote:
Hi Greg,
On Fri, Jul 25, 2014 at 4:20 PM, Greg Flanagan vent...@gmail.com
javascript: wrote
they are done and the parent can go back to
become canHandleMore. You can return a message back to the client from
the noMoreRequest state.
On Friday, July 18, 2014 2:54:45 AM UTC-4, Greg Flanagan wrote:
I have an actor that makes an http call that can take a long time to
complete
I have a List of Futures that I convert to a Future[List[T]] using
Future.sequence. Then on the Future[List[T]] I have an onComplete handler
that I want to get called only once all Futures have completed, regardless
of any failures. The issue that I'm running into is that onComplete is
getting
I have an actor that makes an http call that can take a long time to
complete (i.e. 10 - 30 minutes). I only want to be hitting the service at
most 3 at once so I don't want the actors to consume more messages until
the current call is finished. I've got it all working great using the work
in there or is the service just so slow (or is
it a stream of data)?
On Fri, Jul 18, 2014 at 8:54 AM, Greg Flanagan vent...@gmail.com
javascript: wrote:
I have an actor that makes an http call that can take a long time to
complete (i.e. 10 - 30 minutes). I only want to be hitting the service at
most
I'm using the working pull pattern and wanted to be able to spawn and reap
workers while the application is running. Spinning up new workers is
trivial but I had some questions about terminating current workers.
Currently I'll send a worker a PoisonPill to get it to shut down but when I
do
11 matches
Mail list logo
