by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 17:42
    PatLeong opened #4541
  • 17:35
    PatLeong opened #4540
  • 15:27
    Aaronontheweb labeled #4539
  • 15:27
    Aaronontheweb closed #4539
  • 15:27
    Aaronontheweb commented #4539
  • 03:30
    snrajan edited #4539
  • 03:24
    snrajan opened #4539
  • Aug 10 17:18
    Arkatufus synchronize #4425
  • Aug 08 10:17
    Zetanova edited #4533
  • Aug 07 23:32

    dependabot-preview[bot] on nuget

    (compare)

  • Aug 07 23:32

    dependabot-preview[bot] on dev

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Aug 07 23:32
    dependabot-preview[bot] closed #4538
  • Aug 07 22:00
    Arkatufus synchronize #4531
  • Aug 07 19:27
    dependabot-preview[bot] commented #4538
  • Aug 07 17:52
    dependabot-preview[bot] edited #4538
  • Aug 07 17:52
    Aaronontheweb commented #4538
  • Aug 07 17:52
    dependabot-preview[bot] synchronize #4538
  • Aug 07 17:52
    dependabot-preview[bot] synchronize #4337
  • Aug 07 17:52

    dependabot-preview[bot] on nuget

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Aug 07 17:52

    dependabot-preview[bot] on nuget

    Bump FSharp.Quotations.Evaluato… (compare)

Andrew Skotzko
@skotzko
or /*/Executors to reuse it
under other top level actors
Daniel Ferreira Monteiro Alves
@danfma
You are right! I was dumb here! I forgot that actor is a child of another one!
:D
Andrew Skotzko
@skotzko
no worries :)
key thing is that your actor path needs to be right in the config, so double check that first
Daniel Ferreira Monteiro Alves
@danfma
ok
another question, let me say that I want to create some kind of processors on demand
I created a service with a queue of messages
the actors should pop some messages from time to time
Joshua Benjamin
@annymsMthd
Maybe a pooled router with a resizer?
Daniel Ferreira Monteiro Alves
@danfma
I was thinking in use the router to create that behaviour, while checking from time to time that queue
yes!
that's the point!
I created some actors using the async behaviour
Andrew Skotzko
@skotzko
i guess you could have one actor scheduled to receive messages off the queue and then hand them to a resizable pool router for scalable processing
s/them/the messages
Daniel Ferreira Monteiro Alves
@danfma
that's what the monitor is doing the previous code
the Executors is a pool of actors routed by the monitor
Andrew Skotzko
@skotzko
ah
ok
Daniel Ferreira Monteiro Alves
@danfma
one thing is funny
if I use the async from the .NET then the actors does not respect the default behaviour that only one message is processed by an actor at a time, apparenly
apparently*
is the the right thing when using async or a problem
Roger Johansson
@rogeralsing
What version are you using?
Daniel Ferreira Monteiro Alves
@danfma
the last one
just checking
Andrew Skotzko
@skotzko
default respects one message at at time
Roger Johansson
@rogeralsing
And what async behavior? Suspend or reentrant?
Natan Vivo
@nvivo
this async stuff must be a problem with Brazilians...
Andrew Skotzko
@skotzko
you have to specifically enable reentrant
Daniel Ferreira Monteiro Alves
@danfma
the version on nuget is the 1.0.0
yes, I configured that
kkkkkkkkkkkkk
is there another one here?
Natan Vivo
@nvivo
you should leave the default or specify Suspend
are you using ReceiveActor?
Daniel Ferreira Monteiro Alves
@danfma
yes
I will write one example here, just a moment
Natan Vivo
@nvivo
just do Receive<Foo>(async foo => { .. })
the default behavior is Suspend already
Roger Johansson
@rogeralsing
Btw async await is broken in nuget 1.0 package
Natan Vivo
@nvivo
oh, right!
Andrew Skotzko
@skotzko
but fix coming next week
in 1.0.1
Daniel Ferreira Monteiro Alves
@danfma
ahhhh
Natan Vivo
@nvivo
@danfma I'm Brazilian
Daniel Ferreira Monteiro Alves
@danfma
:D
me too