Hi Ivan,
Will kamon support Socket connections?
Also I looked at http://kamon.io/integrations/spray/server-side/. It was
TODO.
for the record: Kamon does provide metrics on number of HTTP requests,
average, min, max, counts per response status code and more, we don't have
metrics for bytes
Hi √iktor,
I did not mean a full activator sample, but I think a few more words
in the documentation on *how* to achieve getting multiple mediators to
work for a large set of topics and/or subscribers might be helpful
(instead of just mentioning that it is possible). Is some sort of
sharding
You can check spray-client docs here:
http://spray.io/documentation/1.2.1/spray-client/
If only version compatible with the build of play you're using (akka
dependency), I don't see a reason to not use it if you'd like it.
-- Konrad
On Thu, Sep 11, 2014 at 9:00 PM, jitendra shelar
Hi,
Would it not be a good idea to have leveldb as a separate dependency a la
akka-persistence-leveldb? I know one can exclude dependencies,
but I am thinking that most people will use something else for production.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Also, spray-client is when you need http communication.
If the only thing you’re after here is fire-and-forget semantics all you
need is ! (tell), that’s exactly the semantics it has.
Futures are not and forget, because you do get some information in them
(completed / failed).
On Fri, Sep 12,
On Fri, Sep 12, 2014 at 11:46 AM, Remigius Stalder
remigius.stal...@descom-consulting.ch wrote:
Hi √iktor,
I did not mean a full activator sample, but I think a few more words
in the documentation on *how* to achieve getting multiple mediators to
work for a large set of topics and/or
Team,
We are building a reactive application and planning to us akka persistence.
But we are stuck at a point where we have decide between java and scala.
Below are very important questions for my analysis.
Is it better to create actor system or actors in scala or java?
What are the
Thanks Konrad.
I am trying with ! (tell).
*Playframework Code:*
import play.api._
import play.api.mvc._
import akka.actor.{ActorSystem, Actor, ActorRef,Props}
import scala.concurrent.duration._
import play.api.libs.ws.WS
class HelloActor extends Actor {
def receive = {
case hello =
Rune,
I wouldn't knock yourself out using the persistent views (as I did, even
going so far as creating dynamic views upon aggregate creation) because the
design is undergoing some big changes. In my opinion you'd be better off
having an actor listening for the events on behalf of all
If there are any sample examples related to spray-clien and playframework,
please let me know.
I don't want the response back from the Action.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
// After above WS call, I want this view page to be displayed. The
control must not go back to Ok
and
fire and forget
won't work (both principles exclude each other).
Whats your goal? Display the output of the netBankingPage action in the
index action or do some work in the background?
Yes Planetenkiller,
My goal is to display the netBankingPage into my index action.
Problem I am facing is index Action returns http response(Ok).
I just want to call the netBankingPage and end the process at that instant.
I am new to playframework/scala/actor and implementing this application
As Konrad said, I cannot use akka futures here.
I have tried using futures before.
Best suitable for this scenario is akka actors.
But really stuck in between. Not getting how to proceed ahead.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Yes Planetenkiller.
Actor doesn't send http response.
I am not interested in http response in this scenario.
I just want that netBankingPage to be displayed and that's it.
I am not interested in sending response back to action.
If any alternatives/solutions, please let me know.
Thanks,
Jitendra
Dear hakkers,
today we are very excited to share with you another early preview milestone
of Akka Streams and Akka HTTP. Version 0.6 was not widely announced because
we were preparing some major work on the API and most of that is now
finished. Behold, the new FlowGraph DSL (we have implemented
Hi,
In my system, a node keep complained ] Association with remote system
[] has failed, address is now gated for [5000] ms. Reason is: []],
however the node never being started this round. The whole cluster
has been shut down between the rounds.
Does the dispatch has some
Hi Konrad,
We have the same requirement. The reason why we need this approach is
because we need two types of cluster: Web and Processing cluster. Both have
different lifecycles and concerns, but the Web cluster needs to subscribe
to data sources processed by the backend cluster. The
Konrad, isn't TestActorRef valuable for unit testing with actors? This
assumes the proper IT test coverage is there as well as an outer layer of
the onion.
On Wednesday, September 10, 2014 10:16:48 AM UTC-4, Akka Team wrote:
By interacting with them – same as normal Actors.
I would not
Hi,
akka-persistence-testkit has no test for this case, it's an Akka cluster issue
as far as I can tell. Most use cases create snapshots based upon some kind of
counter variable every 100 of journal entries (persist calls) or so, to create
snapshot instances, thus changing the internal state,
Hi Sean,
I personally am not a big fan of TestActorRef (others may disagree - this
may be a matter of taste...), as it changes the timing semantics of the
thing you're testing.
Of course it makes testing (in some cases) easier, but the sacrifice is
that you assume single-threaded execution,
which
Thank you. Your thoughts make sense.
On Friday, September 12, 2014 10:24:36 PM UTC+2, Akka Team wrote:
Hi Sean,
I personally am not a big fan of TestActorRef (others may disagree - this
may be a matter of taste...), as it changes the timing semantics of the
thing you're testing.
Of
I get where you're coming from. People may rely on test with TestActor ref
and not do the proper actor specs. Those IT specs are mandatory.
On Friday, September 12, 2014 4:24:36 PM UTC-4, Akka Team wrote:
Hi Sean,
I personally am not a big fan of TestActorRef (others may disagree - this
may
I get where you're coming from. People may rely on test with TestActor
ref and not do the proper actor specs. Those IT specs are mandatory.
Exactly, you’ve defined it way better than I did by going into the nitty-gritty
details actually :-)
--
Konrad 'ktoso' Malawski
hAkker @ typesafe
23 matches
Mail list logo
