Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 16 16:14
    IgorFedchenko commented #4032
  • Nov 16 13:19
    ismaelhamed synchronize #4042
  • Nov 16 13:17
    ismaelhamed commented #3863
  • Nov 16 11:47
    IgorFedchenko synchronize #4032
  • Nov 16 11:47
    IgorFedchenko commented #4032
  • Nov 16 11:21
    ismaelhamed synchronize #3863
  • Nov 16 11:17
    ismaelhamed edited #3863
  • Nov 16 11:17
    ismaelhamed synchronize #4042
  • Nov 16 09:58
    IgorFedchenko synchronize #4032
  • Nov 16 09:49
    IgorFedchenko synchronize #4032
  • Nov 16 09:45
    IgorFedchenko commented #4032
  • Nov 16 09:17
    ismaelhamed opened #4043
  • Nov 16 09:03
    ismaelhamed opened #4042
  • Nov 16 09:03
    IgorFedchenko commented #4032
  • Nov 16 08:59
    IgorFedchenko synchronize #4032
  • Nov 16 08:57
    IgorFedchenko synchronize #4032
  • Nov 15 22:35
    Aaronontheweb commented #4032
  • Nov 15 20:26
    IgorFedchenko synchronize #4032
  • Nov 15 20:24
    IgorFedchenko commented #4032
  • Nov 15 20:06
    IgorFedchenko synchronize #4032
Damian Reeves
@DamianReeves
Concerning PipeTo: If my intent is to allow my Actor to continue processing other messages while a long running task runs, then I don't need to use PipeTo correct?
Bartosz Sypytkowski
@Horusiath
@DamianReeves
  1. Don't introduce concurrency on an actor level. You'll introduce all problems of concurrency actors are supposed to solve. If you have long running tasks, isolate them in dedicated actors.
  2. PipeTo is used by and actor to keep up with task completion acknowledgements. You can use it without problems.
Damian Reeves
@DamianReeves
@Horusiath thanks. Point 1. has been my preferred approach, but I wasn't sure if something else was preferred.
So if I need to write a file from records in a database I do:
  1. Create an Actor for the whole process, lets call it DataWriterActor
  2. Create a child of DataWriterActor called DataExtractor
  3. Do data access in DataExtractor
  4. Tell parent of results
    Is this the recommended approach?
Bartosz Sypytkowski
@Horusiath
except making them a parent/child relation, yes :)
Damian Reeves
@DamianReeves
You keep them totally independent?
Bartosz Sypytkowski
@Horusiath
both of those actor types are making potentially risky operations, you could supervise them with dedicated parent actors and simply keep an actor ref between them
Damian Reeves
@DamianReeves
Ok got it
Roger Johansson
@rogeralsing
@skotzko what is the new "ready" label about ? it shows up on tasks that are not yet started so that seems odd
Weston
@ronnyek
so with the io shit, can the actors be multiplexed against same port on same ip?
or is it like the actors host the tcp endpoint?
Sean Killeen
@SeanKilleen
@rogeralsing maybe "ready" in the sense that tasks are ready to be worked on (e.g. acknowledged / explained enough)? Just spitballing a guess.
Roger Johansson
@rogeralsing
ah, that could be it
Sean Gilliam
@sean-gilliam
@Coinio you could be the first to write such an example ;)
Aaron Stannard
@Aaronontheweb
@Horusiath put them into separate tasks because I'm asking some of our newer contributors to take them on - this makes it easier to assign them
@GeertVL all of these issues are available for work - we'd really appreciate your help with them: https://github.com/akkadotnet/akka.net/labels/akka-remote
Coinio
@Coinio
@sean-gilliam Once I'm done with the bootcamp I'll definitely give it a go
Geert Van Laethem
@GeertVL
@Aaronontheweb can you tell me why you closed #1136 without merging. I want to learn from the mistake I made.
Aaron Stannard
@Aaronontheweb
@creepone we need to port the following spec to verify that the UID changes: akkadotnet/akka.net#1254, and this one for remote deathwatch akkadotnet/akka.net#1251
but even in the event of an unplanned termination, you should still get the deathwatch notification
@GeertVL yeah, I couldn't merge it into dev due to a merge conflict - asked you to do a rebase on dev a couple of weeks ago and never heard back
which would have resolved the issue
Geert Van Laethem
@GeertVL
@Aaronontheweb sorry I was on vacation.
Aaron Stannard
@Aaronontheweb
I figured you were busy
no worries man
you didn't do anything "wrong"
but I ended up needing that PR for something I had to work on
so I incorporated that change into one of mine
Geert Van Laethem
@GeertVL
@Aaronontheweb do I still try to fix it or is it done now?
Ha ok. That answers my question
Ok I look at the issues on akka-remote.
Aaron Stannard
@Aaronontheweb
thanks man, we'd really appreciate that
if you have any questions about what to do with those issues, you can always ping me in here or if you'd like I can give you my Skype info
Geert Van Laethem
@GeertVL
On a side note, Is it wise to study scala and Akka to be more of a help with akka.net?
Yes please that makes it easier.
Aaron Stannard
@Aaronontheweb
through the act of trying to port Akka to .NET, you'll end up learning a lot of Scala that way
Geert Van Laethem
@GeertVL
I thought so.
Aaron Stannard
@Aaronontheweb
for instance, they have their own version of the TPL (Scala Futures)
Geert Van Laethem
@GeertVL
ok
Aaron Stannard
@Aaronontheweb
which actually acts and behaves a lot like ours, but the names for things are a little different
Geert Van Laethem
@GeertVL
I see.
Aaron Stannard
@Aaronontheweb
the thing that, to this day, still trips me up though is that Scala has something like 200+ binary and ternary operators
for doing things like immutable list appends / removes
all sorts of stuff - makes the Scala code really concise but sometimes I find myself scratching my head
you'll pick it up faster than you might think though!
Geert Van Laethem
@GeertVL
Ok but reading the book "Scala for the impatient" that I bought should be helpful :-)
And my skypehandle is geertvanl
Aaron Stannard
@Aaronontheweb
cool, I'll add you
Geert Van Laethem
@GeertVL
Tx Aaron
Aaron Stannard
@Aaronontheweb
mine is the same as my Gitter handle
Geert Van Laethem
@GeertVL
easy :-)