|
||||||||
|
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'm working on this with Pascal. We prefer to have this very small API inside the UI to avoid the need to deploy an additional webapp (REST) only for this need. When the REST webapp will be more stable and widely adopted we can just remove this redundancy.
The main use case that we try to achieve is the following
1 daemon handle server MANY running dspace repository anyone with its own handle prefix
If the dspace database is running behind a customer firewall the daemon handle server running centrally on the service provider network is not allowed to access the database.
We want to avoid to setup an handle server on the customer side any time as security constraints, policies and different S.O. make this activity time consuming.