by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 01:12
    to11mtm opened #4512
  • Jul 10 23:43
    Arkatufus commented #4511
  • Jul 10 23:36
    Arkatufus commented #4506
  • Jul 10 23:36
    Arkatufus closed #4506
  • Jul 10 23:35
    Arkatufus commented #4511
  • Jul 10 23:29
    Arkatufus edited #4511
  • Jul 10 23:29
    Arkatufus converted_to_draft #4511
  • Jul 10 23:28
    Arkatufus opened #4511
  • Jul 10 09:45
    petrikero opened #4510
  • Jul 10 09:17
    petrikero opened #4509
  • Jul 10 07:33
    ismaelhamed commented #4419
  • Jul 10 05:25
    ismaelhamed commented #4419
  • Jul 10 01:20
    Aaronontheweb commented #4419
  • Jul 10 01:03
    to11mtm commented #4419
  • Jul 09 23:40
    Aaronontheweb commented #4508
  • Jul 09 23:40

    Aaronontheweb on dev

    Fix source links in documentati… (compare)

  • Jul 09 23:40
    Aaronontheweb closed #4508
  • Jul 09 23:40
    Aaronontheweb closed #4482
  • Jul 09 23:40
    Aaronontheweb closed #4497
  • Jul 09 23:39
    Arkatufus commented #4497
Aaron Stannard
@Aaronontheweb
which version of Akka.Persistence is this plugin using?
Chris Martin
@trbngr
103 I believe
1.0.3.0-beta
Aaron Stannard
@Aaronontheweb
ok, so it's the latest then
Chris Martin
@trbngr
Not a super huge deal. I'm just trying to avoid the constant polling of the persistence journal.
and use the ES subscirptions
Aaron Stannard
@Aaronontheweb
the PersistentView is getting replaced is it not cc @Horusiath
so how does EventAppeard get called?
Aaron Stannard
@Aaronontheweb
do you really care about the Sender in this case?
because that's what is throwing
you could try passing in ActorRefs.NoSender
for the sender on that tell
and that should work
Chris Martin
@trbngr
oh yeah. lemme try that
HO LEE FUK! It lives! :P
Thanks so much, dude
Aaron Stannard
@Aaronontheweb
anytime
Sender, Self, Parent all use Context
Chris Martin
@trbngr
Right on
Aaron Stannard
@Aaronontheweb
and Context is bound the to ExecutionContext of the actor
so you can't really access Context in an async call or Continuation
can only be called inside the Receive methods
Chris Martin
@trbngr
So I don't need to capture _self? I can just use Self. Noted
Aaron Stannard
@Aaronontheweb
no
you do need to capture Self
because that's part of the context too :p
Chris Martin
@trbngr
well crap. haha
Am I right to capture it in PreStart?
Aaron Stannard
@Aaronontheweb
yeah
the Context is active there
Chris Martin
@trbngr
nice. This is pretty bad ass
Aaron Stannard
@Aaronontheweb
basically anything inside the actor is safe
it's when you start trying to use the Context outside of the actor's running scope where things get weird
Chris Martin
@trbngr
cool
Chris Martin
@trbngr
Optimized Akka.Persistence.EventStore. It will now use only one IEventStoreConnection per the ES docs. I also add an implementation of PersistentView called EventStoreSubscriptionView that uses an EventStoreSubscription to stay up to date instead of an PersistentView.AutoUpdateInterval
Still no tests, however ;)
Chris Martin
@trbngr
Is there a way to grab a ILoggingAdapter from an ActorSystem? I need one pretty early
:blush: system.Log
Thomas Lazar
@thomaslazar
@Aaronontheweb: i know apache thrift employs or better recommends an extend-only design of their interfaces. to make it backwards compatible to an extend
they have numbered fields in their definitions that you're not supposed to change on edit. and just extend with new numbers
varghesep
@varghesep
I don't normally get any response for the questions that I post here. They get lost in this chat. So I posted some code on Stack Overflow at http://stackoverflow.com/questions/30956153/service-fabric-akka-net-and-persistent-actor-integration
Please share your comments, improvements needed so everyone can learn from it. The example has the integration of Service Fabric, AKKA.NET and Persistence.
Roger Johansson
@rogeralsing
@Horusiath under what conditons does akka.persistence need to serialize journal/snapshot with special transport information?
Weston
@ronnyek
So i've been lookng a bit into project orleans, and it seems like its much much more targetting the idea of basically short lifecycle fire up a grain, change state persist state dismiss
not so much having a distributed pool of workers
so I'm wondering if akka.net is more for that. Seems like its a good way to manage a distributed pool of workers, with managers at certain levels
Error handling etc
Roger Johansson
@rogeralsing
@ronnyek there is a great comparison of akka vs orleans here https://github.com/akka/akka-meta/blob/master/ComparisonWithOrleans.md
written by Roland Kuhn (jvm Akka lead) and proofread by the orelans team