Skip to content
This repository has been archived by the owner on Feb 3, 2018. It is now read-only.

Create an internal source manager decorator for caching #14

Closed
sdboyer opened this issue Apr 25, 2016 · 1 comment
Closed

Create an internal source manager decorator for caching #14

sdboyer opened this issue Apr 25, 2016 · 1 comment
Milestone

Comments

@sdboyer
Copy link
Owner

sdboyer commented Apr 25, 2016

In order to keep the main sourceManager as agnostic to the particular project it's solving for as possible, we need a separate SourceManager decorator-style object that is created internally on each Solve(), and can become responsible for handling things like #13 .

This architectural improvement will let us keep the solve-specific logic separate from the system-tracking logic. Another example would be caching the sorted, computed version list based on the solve direction.

@sdboyer
Copy link
Owner Author

sdboyer commented Apr 28, 2016

This has architectural value beyond just the performance. It'll help keep the layers separate with #10 , for example. So, making it part of MVP.

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

No branches or pull requests

1 participant