justin-lovell / act-it Goto Github PK

The Domain layer might not take on a dependency for the TellIt library. Instead, we could generate a callback Func for the domain layer to notify TellIt to do its thing.

We initiate some of those tasks

Interrupt method - will ask the SceneActor to stop what it is doing and allow listeners to act on the event immediately. Useful when implementing a disconnected pub/sub

Like in the Semantic-Pipes, it is useful to have this implemented as a first prize.

Unlike the Semantic-Pipes, there will be a lot of concepts which will rely on the async keyword. Unfortunately, should the tell-it project attempt to target .NET 4.0, then we may be in for a more difficult time.

We have a concept of listeners onto a story-line. What if we can just fire a hose pipe at an "eaves dropper".

The "eaves dropper" could be useful when building tests to ensure that all the expected events were fired, and no other events managed to slip in. You know... those aunts who will always correct the story line :)

Some methods could allow nulls to be passed into methods, but the implications of the non-null expectation could only be realised much later.

It may be too convenient for the tasks to become a run away train if client developers do not use the await keyword upon their Interrupt method calls.

Let's keep track of all those tasks and ensure that the primary SceneActor keeps track of all the tasks.

Consider replacing the nested calls to a stack of some sort