Feature/processes - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a replacement for the component based on the "Process" design.
This design uses a concept of "channels" to represent data that are being changed by objects and affect each other.
For example you might have an object that receives a message from the user and returns a message in response.
We can represent that with an input channel and an output channel that are processed by the object.
The object reads from the input channel the message from the user, and modifies the output channel to have it's response.
This design is superior to the "Component" based design in my opinion because it eliminates the concept of input and output, and makes it easier to have multiple inputs, multiple outputs, and have different channels being processed in different ways.