Fetching a release's tracklist should be a separate end point

metabrainz / web-service-v3-design

A collaborative specification for the third version of the MusicBrainz web service

2 stars 1 forks source link

Fetching a release's tracklist should be a separate end point #21

Open ocharles opened 12 years ago

ocharles commented 12 years ago

To get all tracks for a release, clients should query something other than /release/:mbid, allowing consistency for the /release/:mbid end point. Questions:

What end points? I propose just ./tracks
Should it be paginated? I'm tempted to say no.

warpr commented 12 years ago

I would prefer a non-paginated endpoint for each medium or tracklist. A tracks endpoint which gives all the tracks on a 200 CD Mozart box would be considerably larger than the other responses we have in /ws/3, segmenting this per disc seems like a good way to get the response size closer to other requests.

(That would also map better to how e.g. the release editor deals with those cases, the release editor loads the tracklist for a medium on demand, when the medium is expanded)