![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
DSpace API, JSPUI, XMLUI |
|
Created:
|
22/Aug/13 10:45 AM
|
|
Description:
|
For security reasons we want to run the handle server and the application container on separate machines. This would even be helpful for institutions running multiple DSpace instances as they would need one handle server only for all instances.
We want the HandlePlugin to connect to a DSpace instance over http(s) instead of using the HandleManager directly. The handle server could run on a separate machine and would neither need access to the HandleManager nor need a database. XMLUI and JSPUI could serve the required information as JSON.
DS-1171 has a similar idea with a different approach. They want the HandleManager to store the handles in an external handle server. This is interesting if you want to use one handle server for DSpace and other software, but it would need some bigger changes to the HandleManager and it would duplicate the information about used handles over two different databases (the database DSpace uses and the database the external handle server uses).
|
|
Project:
|
DSpace
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Pascal-Nicolas Becker
|
|
|
|
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
