|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
I intentionaly phrased Step 4 that way to make it an explicit, one-time user action during installation to phone home. Thus no configuration option would be necessary.
While there could be an option to disable exposing information via REST (Step 3), this endpoint can be simply hidden by standard means (web server/webapp configuration).
> REST interface, it should not be part of any existing UI
I agree. Again, I tried to phrase it that way. In brackets I explore whether we should handle the situation when user wishes to expose only one of the webapps (hide the REST webapp).