Open jdnarvaez opened 6 years ago
That's a very interesting idea... thanks for contributing!
My initial thought was to just allow there to be a registered 'content manager' that would handle all of the load image/load and cache image requests, but I didn't think there was an 'elegant' way to do that without simply making it seem like the load image logic is being short circuited. I've been using the method on my own for a few weeks and it seems to work, so I can create a PR for it for review and approval/rejection.
@jdnarvaez Thanks for adding information, and for a PR! Any/all help with these repositories are greatly appreciated (:
I've added some notes to your PR 👍
I'm not sure my current implementation of the content manager API would make sense, as much of it retrieves content from proprietary APIs but I could probably create one with a caching layer implemented for the CornerstoneWADOImageLoader if that would help clarify things, just might take a little time.
It would be nice if we could register an image loader that did not use the cornerstone image cache so that various levels of caching could be implemented by the consumer instead.