Gabriel Kliot

I have added a section "Dealing with libraries" to http://dotnet.github.io/orleans/Advanced-Concepts/External-Tasks-and-Grains. Hopefully it will be more straightforward now. You have no idea (or maybe you do) how lucky you/we are to...

I think that is exactly what we agreed upon and planned to do a long time ago. That is at least what I remember.

Yes, as reference. No, it has to be exposed via interface. But you can define a different interface, it can be internal in the grain impl. assembly.

Added documentation here: http://dotnet.github.io/orleans/Orleans-Streams/Streams-Programming-APIs Stateless Automatically Scaled-Out Processing.

@rore, I think in your case you can't really use `StatelessWorkers`. If I understand your case correctly, you need to reliably send "invalidate" command to all read replicas and make...

Lets talk about `StatelessWorkers` here and open a separate issue about replication. It is a big enough issue to deserve its own thread. OK? So please go ahead and open...

Guys, lets not combine 2 unrelated threads please, OK? Just makes later following and reasoning so hard. This thread is about `StatelessWorkers` using streams. A different issue is replication and...

@rore, about `StatelessWorker` abstraction with streams. First, lets assume we are talking about Explicit subscription, and not Implicit. So first the GRAIN has to subscribe, at least once. Otherwise, no...

With implicit subscription the grain is already subscribed, statically. You still need to call `SubscribeAsync` from `OnActivateAsync`, but this is only attach the `IAsyncObserver`, not to do any actual grain...

I think this is again unrelated to stateless workers. For regular grain we can have an additional option: `IAsyncStream.SubsribeTransientAsync()` and it will be a transient subscription for this activation only....