Hi,
On 4 November 2013 09:13, Kostas Stamatis kstama...@ekt.gr wrote:
1) REST API versioning
---
As read from some sites and blogs, the versioning of a REST API can be
denoted either in the URL or in the mime type of the HTTP communication (in
the ”Accept” and
Dear developers,
I have some comments, regarding the Jersey Rest API, after a discussion we
had with Peter Dietz in the dspace IRC channel some days ago.
1) REST API versioning
---
As read from some sites and blogs, the versioning of a REST API can be
denoted
Hi Kostas,
here my viewpoint
1) I prefer the header method. A missing header should be read as the
current version.
2) I agree with you. It is usually to find a common template across REST
API implementation and we should follow the common practice
3) Detailed errors information are desirable
Hi Kostas,
Thanks for drawing attention to this, I would love the developer community
to give input on this, so that we end up with a more acceptable product. I
would say the current status of the REST API is acceptable, and certainly
gives us the ability to do new things with DSpace. Its some of
After several months of development, Wijiti is pleased to contribute
this reworked version of the REST API for DSpace 1.8.x.
Details and documentation are available at https://jspace.atlassian.net/
and all code is freely available via Github, the link of which is in the
documentation.
Enjoy.
This page shows the proposed REST API for DSpace 2. The work is being
done as part of the google summer of code and DSpace 2 efforts.
http://wiki.dspace.org/index.php/Google_Summer_of_Code_2009_DSpace_REST_Webapp
It is still a work in progress but this draft should cover most of the
core
