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

Create a plugin registry for multiple accessors #2

Open
sirpalee opened this issue Aug 1, 2017 · 2 comments
Open

Create a plugin registry for multiple accessors #2

sirpalee opened this issue Aug 1, 2017 · 2 comments

Comments

@sirpalee
Copy link
Contributor

sirpalee commented Aug 1, 2017

We need a generic plugin registry that can load up multiple accessors easily, and provide an interface that's flexible and easy enough to customize.

@chadrik
Copy link

chadrik commented Aug 1, 2017

Should the plugins just be other ArResolvers that are delegated to by the master ArResolver?

@sirpalee
Copy link
Contributor Author

sirpalee commented Aug 1, 2017

If you want the most flexible option, then yes.

However, I think we could do equally good by only exposing parts of the interface and limit the scope of each accessor. For example, I would like to generate the temporary file location on the disk using the URIResolver and making sure they are removed once the URIResolver is out of scope, so accessor don't have to worry about such problems. Same goes for encryption of passwords for database based accessors.

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

No branches or pull requests

2 participants