Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CurationConcerns Actors are not Actors #864

Open
barmintor opened this issue Jun 26, 2016 · 1 comment
Open

CurationConcerns Actors are not Actors #864

barmintor opened this issue Jun 26, 2016 · 1 comment

Comments

@barmintor
Copy link
Contributor

Descriptive summary

CurationConcerns introduces an abstraction for chaining discrete tasks under a common interface in service of constructing a result object. This is generally referred to as a Chain-of-Responsibility pattern, but we are calling them Actors. Actor is another pattern for dealing with concurrency via message-based computational primitives- just similar enough to be confusing to a new developer that searches for "ruby actor pattern". CurationConcerns::Actors should be renamed in the next major release.

@barmintor
Copy link
Contributor Author

I was talking about concurrent processing in Python and Ruby with @cmh2166, and this misnaming was a point of confusion. It's an impediment to new contributors coming from other languages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant