-
Notifications
You must be signed in to change notification settings - Fork 1
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
make reasonable defaulf without sparql access #4
Comments
Is this related to address the situation when an instrument factory fails? If so, I might have an idea on how to tackle it, I could give it a try and you tell me what you think. |
In principle, I want to address it in a very particular way, with no change to the plugin code. It's important for the general scheme. |
I actually had in mind to apply a change to plugin(s) code. A small change (just in the exposer) that would expose the name of the various plugins. But my idea does not address the situation when sparql access is not available, simply avoid calling the instrument factory for each installed instrument. |
On one hand, that could be useful on it's own, if it does not break something else. |
it would be a small stability improvement. I do not not know if is worth doing it now, unless it is really easy. |
Ok I will try a quick implementation (requires small change on both plugins, and the dispatcher-app) |
#11 tries to address the issue |
No description provided.
The text was updated successfully, but these errors were encountered: