Bill Poole

Thanks very much @FlorianHockmann! I was curious as to what the `E2` generic type parameter should be for the for the `GraphTraversal.Properties.Properties()` method. I figured it should always return a...

Sorry one further question, I couldn't find any documentation that stated whether a series of async traversals will execute on the server in the same order that they are sent....

>I also have found it hard to find definitions for the S and E type parameters for GraphTraversal. They don't seem to have any definition in the XML comments or...

Thanks @ReubenBond. My main concern is the host running out of memory if inbound requests are queued at the receiving grain while waiting for the rate limiter / semaphore. If...

My specific situation relates to Orleans cluster ingress from the Internet. JSON event messages are posted to a cluster of web servers over HTTP 1.1, and those web servers each...

Thanks @ReubenBond for such a detailed reply! I think applying flow control at the host/process level would be fine for most situations - it would be fine for my scenario....

Okay, but the defensive copy isn't needed until the target grain method is invoked, unless the goal is to protect against the message object being mutated before the `Task` returned...

> the grain might continue execution without awaiting the call That's what I meant when I said "unless the goal is to protect against the message object being mutated before...

> At this point, it's worth noting that there is a difference between a regular async method and a grain method. A regular async method will begin execution immediately and...

> It's also speculation that this will be problematic. Some additional context I can provide at this stage - some grains under maximum load will receive about 50,000 calls per...