I really just want to gracefully migration from v1 syntax to v2. (In
reality it's more of v1 to v1.1, where one or two things cause some
incompatibility), i.e. getting parent community list or something is named
slightly differently, and/or to get subcollections you would need to call
another endpoint to get the data: /communities/:id/collections
I'm thinking the same /rest webapp could include both v1 and v2 routes,
just put them into another package, and annotate the routes. It's just this
is extra effort, it adds to the maintenance burden, it causes the api to be
less simple, and I'm just planning to deprecate/remove the v1 stuff, and
make v2 the new default. So, just a crutch so that you don't break your
rest consumer apps. Which is why I'm wondering if this is even necessary.
________________
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Mon, Oct 13, 2014 at 12:11 PM, helix84 <heli...@centrum.sk> wrote:
> Hi Peter,
>
> On Mon, Oct 13, 2014 at 5:19 PM, Peter Dietz <pe...@longsight.com> wrote:
> > i.e. DSpace 4 Read-Only API to be available at: /rest/v1
> > and DSpace 5 CRUD API to be available at: /rest/v2
>
> this (ability to request a particular API version) makes sense only if
> you're going to expose both API versions in DSpace 5. Which would be
> great, but is this what you're going to do? OTOH, if you're only
> informing the user of API version, just make it part of the response
> (e.g. <api-version>5</api-version>) to an info endpoint (a.k.a.
> Identify in OAI-PMG or servicedocument in Atom).
>
> Regards,
> ~~helix84
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel