aabs / actorsrcgen Goto Github PK

i.e. allow the definition of generators that produce a stream of data, but don't require input.

Follow the technique used here

Allow an actor to have multiple start blocks, to allow multiple kinds of inputs to be fed into the pipeline

If a step method accepts a CancellationToken, then provide an/the external cancellation token of the actor to allow the internal actions to be gracefully shut down.

support the swallowing of exceptions for long-running pipelines that cannot afford to be prematurely terminated by unhandled exceptions

i.e. allow data to be distributed down multiple paths using broadcast blocks

Post should not return anything, and should deliver to the input block asynchronously

When no Final step has been defined, the buffer will eventually overflow. Consider creating a synthetic step based on the NullTarget to receive and drop all final messages

i.e. a shorthand for await actor.OutputBlock.ReceiveAsync()

Allow the use of actions as the final step.

Create a new Receiver attribute that is used to generate code to receive incoming messages. The attribute is attached to an initial step and acts as a message pump, getting messages and injecting them into the pipeline.

Try to provide a nice way to declaratively specify an initial step of a pipeline, where the inputs come from a subscription to some external system, such as from MQTT, Event Hub, Kafka, Wolverine etc