Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 15:42
    Aaronontheweb synchronize #4086
  • 15:42
    Aaronontheweb closed #4083
  • 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • 15:42
    Aaronontheweb closed #4089
  • 15:42
    Aaronontheweb labeled #4093
  • 15:42
    Aaronontheweb labeled #4093
  • 15:42
    Aaronontheweb labeled #4093
  • 15:42
    Aaronontheweb opened #4093
  • 14:20
    Aaronontheweb commented #4092
  • 14:14
    Aaronontheweb labeled #4089
  • 14:14
    Aaronontheweb labeled #4089
  • 14:11
    Aaronontheweb synchronize #4089
  • 14:10
    Aaronontheweb synchronize #4086
  • 14:09

    Aaronontheweb on dev

    Convert to ImmutableHashSet for… (compare)

  • 14:09
    Aaronontheweb closed #4090
  • 12:04
    nagytech synchronize #4092
  • 11:53
    nagytech synchronize #4092
  • 11:49
    nagytech edited #4092
  • 11:40
    nagytech opened #4092
  • 11:32
    nagytech edited #4091
Bartosz Sypytkowski
@Horusiath
I mean a lot, when you have to deep dive into internals or have some problem
Natan Vivo
@nvivo
all I got from the docs is "it's the engine that makes akka tick".. all the rest I'm going through the source
yep, exactly
I agree they are useful. but it's not what akka.net needs to attract new people
I tried to explain akka.net to some friends, they have a lot of questions that I only know because I'm here everyday and reading the issues and going through the source. it's not a good path for everyone
Arjen Smits
@Danthar
Yup. And not everything is updated for 1.0 yet. Or so it seems. Sometimes hard to judge, other than the fact stuff could be more clear.
Natan Vivo
@nvivo
writing code is easy. it's much harder to document it =)
Arjen Smits
@Danthar
heh, they respond with 'thats very interesting' and leave it at that :P
they deal with very different problems than me :P
Natan Vivo
@nvivo
my wife calls me the king of nerds, and I come here and I see I'm not half of what it takes to code some of this stuff haha
you guys win hands down
Arjen Smits
@Danthar
I know the feeling. In the land of the blind, the man who can see is king
Natan Vivo
@nvivo
:-p
Arjen Smits
@Danthar
And the fact that this profession has an huge amount of interest areas
jcwrequests
@jcwrequests
Nikita Tsukanov
@kekekeks
Oh, thanks
jcwrequests
@jcwrequests
I have been playing around trying to find a good way to do stateful actors in a hierarchy. After talking with @Aaronontheweb that HashPooling was not a good idea so I came up with a sample project. Besides adding become logic I was wondering if anyone had any thoughts or criticism on how to model this using Akka.
I was going to combine some of the ideas with what @rogeralsing posted in his blog. Anything anyone would like to share is welcome.
Arjen Smits
@Danthar
Any known issues with Akka running on .Net 4 ?
Roger Johansson
@rogeralsing
Dont think anyone have tried tbh
Arjen Smits
@Danthar
yeah me either
when I start thinking about it. There might be some TPL stuff
and there would be some minor perf issues in places where the concurrent collections are used. Those where horrible in perf in .Net 4
meh horrible is a bit much. But they weren't great.
Arjen Smits
@Danthar
Do you guys make .Net 4 builds ?
ah, nuget says nope.
So in short: No known issues, but its not officially supported.
ugh! I hate this: https://skillsmatter.com/skillscasts/4081-greg-young-4081 "Because of its privacy settings: This video cannot be played here"
Arjen Smits
@Danthar
@nvivo the new routing docs are great. But could use some extension on what resizers are and how they work.
Natan Vivo
@nvivo
@Danthar, I'll take a look at that. Thanks
Arjen Smits
@Danthar
@rogeralsing question. About DI and scopes. Currently the docs say that Actors must not have the singleton scope, since its not supported
However, that implies that other scope types are supported. But I think thats wrong, because as far as i understand it
only the transient scope is supported.
Due to how Akka works with location transparency and the lifetime of actors
but i could be wrong :P so im asking ;)
Roger Johansson
@rogeralsing
You can still remotedeploy DI actors, the DI will occur on the remote system as the DI support is based on actor producers
Assuming the correct config exists on the remote system that is
Natan Vivo
@nvivo
@rogeralsing so DI shouldn't affect remoting or clustering?
Arjen Smits
@Danthar
@rogeralsing Ah I remember reading about that. But that is not what I was referring to.
Roger Johansson
@rogeralsing
I havent tried it our but in theory it should work just fine as the props that are pushed to the remote system only contain the typename for the actor producer
Arjen Smits
@Danthar
lets assume a non-remoting/clustering scenario for now.
lets say you are using an actorsystem in asp.net
Arjen Smits
@Danthar
and you register your actors with an DependencyPerHttpRequest scope
Gerjan
@GerjanOnline
Roger, who are these people?
Roland Kuhn?
Arjen Smits
@Danthar
which would mean that the actors are disposed at the end of an httprequest. What i'm thinking is that this cannot work.
Roger Johansson
@rogeralsing
@GerjanOnline yes, Roland Kuhn (akka lead for typesafe) holding the akka frame there.. no idea who the others are
Gerjan
@GerjanOnline
okay thanks
Roger Johansson
@rogeralsing
@Danthar hmm yes that sounds weird.. I have look that up