You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of what we had in mind during the development of our Lucene plugin, we lack the means of reconfiguring a plugin while Dicoogle is running. I propose that we expose this feature with a web service and internally via the SDK. Something like this:
Getting: GET/management/settings/plugin/<plugin-name> : would return an XML document
Setting: POST/PUT/management/settings/plugin/<plugin-name> : I'm not sure how I'd design this one. Providing a full XML document in the HTTP body is impractical because the user might only need to redefine one property. On the other hand, defining an XML element is more than just a key-value pair.
ConfigurationHolderDicooglePlatformInterface#getPluginSettings(StringpluginName);
// not sure about this one eitherDicooglePlatformInterface#setPluginSettings(StringpluginName, ConfigurationHolderconfig);
Let us use this issue to make a decision on the API.
The text was updated successfully, but these errors were encountered:
As part of what we had in mind during the development of our Lucene plugin, we lack the means of reconfiguring a plugin while Dicoogle is running. I propose that we expose this feature with a web service and internally via the SDK. Something like this:
Getting: GET
/management/settings/plugin/<plugin-name>
: would return an XML documentSetting: POST/PUT
/management/settings/plugin/<plugin-name>
: I'm not sure how I'd design this one. Providing a full XML document in the HTTP body is impractical because the user might only need to redefine one property. On the other hand, defining an XML element is more than just a key-value pair.Let us use this issue to make a decision on the API.
The text was updated successfully, but these errors were encountered: