-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add package and module structure #7
Conversation
…ent), move "scope" and "multitask" out of "context" package, rename "multitask" to "operation"
… intro to auto-managed attribute scopes
…ibute names; also revise intro text
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general I think the architecture is structured fine with a good division between the manager and worker components. I have said in a few places that code can be made to generically handle either threads or processes using shim types and the fact that the multiprocessing primitives (lock, pip, queue, shared memory, etc.) work just fine with threads so using them everywhere doesn't hurt. I had written a bit about the buffer definition that you have and would suggest rethinking this after reviewing how Queue works and also looking into using the Pipe primitive directly. Shoving huge amounts of data down queues or pipes isn't a great idea so consider using shared memory for that.
Closes #6
master