Opened 10 years ago

Closed 9 years ago

#550 closed enhancement (fixed)

Use Java Handle API to resolve handles?

Reported by: Twan Goosen Owned by:
Priority: major Milestone: VLO-3.2
Component: VLO web app Version:
Keywords: Cc: teckart@informatik.uni-leipzig.de

Description (last modified by Twan Goosen)

The current HandleClient implementation is HandleRestApiClient, which uses the handle.net REST API to resolve "hdl:" URI's. Using the Java Handle API library instead may have measurable performance benefits - but also some potential complications depending on the network setup (mainly due to firewall settings). Investigate.

See #136 for some comments and potential issues with using the Java API.

Change History (6)

comment:1 Changed 10 years ago by DefaultCC Plugin

Cc: teckart@informatik.uni-leipzig.de added

comment:2 Changed 10 years ago by Twan Goosen

Description: modified (diff)

comment:3 Changed 10 years ago by Twan Goosen

Description: modified (diff)

comment:4 Changed 10 years ago by Twan Goosen

Priority: minormajor

The corpus structure 2 core library of the LAT archive (TLA-MPI) has a HandleResolver interface with a Handle API based implementation. There is also a caching wrapper. These could be used off the shelf, maybe it should be split off into a separate library though (by the TLA developers).
Consider temporary caching (expiry time ~12h?) of handle resolution results.

comment:5 Changed 9 years ago by Twan Goosen

Milestone: VLO-3.1VLO-3.2

Splitting 3.1 milestone. Most open tickets go to 3.2 so that we can have a release on the short term.

comment:6 Changed 9 years ago by Twan Goosen

Resolution: fixed
Status: newclosed

Fixed in r6192

Note: See TracTickets for help on using tickets.