Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-586

Way to identify an application using the webservice

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • ws/3
    • NGS - Beta 1
    • Web service
    • None

      With the current Musicbrainz system you have to specify a clientid (consisting of application name and version) when submitting puid/mbid pairs but not for submitting another data or for retrieving data from the web service.

      I think this idea should be introduced for all retrieval and submission of data, but it needn't be mandatory. Might need a more sophisticated authentication method then that the current system. This would give following advantages:

      1. Would be useful for Musicbrainz and Software providers to seem how much traffic their application is generating.
      2. Would allow requests/submissions from an app to be blocked by Musicbrainz or because at the request of the application provider if they realised there was an issue with a particular version of their app.
      3. Could enable different service level for different applications.

          [MBS-586] Way to identify an application using the webservice

          MonkeyPython added a comment - - edited

          we no longer do puid, the webservice is much more modern, this ticket predates NGS! check if this is still valid

          MonkeyPython added a comment - - edited we no longer do puid, the webservice is much more modern, this ticket predates NGS! check if this is still valid

          Kuno Woudt added a comment -

          Kuno Woudt added a comment - Moving to Post NGS, as discussed on irc yesterday: http://chatlogs.musicbrainz.org/musicbrainz-devel/2010/2010-04/2010-04-26.html#T19-29-57-300238

          Robert Kaye added a comment -

          This should be done for NGS since this has implications on possibly creating a pay WS without rate-limiting.

          Robert Kaye added a comment - This should be done for NGS since this has implications on possibly creating a pay WS without rate-limiting.

          Kuno Woudt added a comment -

          I agree this should be added, but we need to define the exact purpose for it and what exactly we want clients to submit. We talked about API keys and such at the summit, I expect one reason to use those is to easily block misbehaving clients (who don't follow the 1-second rule for example).

          I think this needs more discussion, and is ultimately up to ruaok to decide what exactly is needed from clients and why. So I'm assigning this to you, ruaok.

          As a sidenote, I definitely support making clientid statistics available to the public. When I wrote a last.fm plugin back in the audioscrobbler days it was very interesting to see on audioscrobbler how many users were using my plugin.

          Kuno Woudt added a comment - I agree this should be added, but we need to define the exact purpose for it and what exactly we want clients to submit. We talked about API keys and such at the summit, I expect one reason to use those is to easily block misbehaving clients (who don't follow the 1-second rule for example). I think this needs more discussion, and is ultimately up to ruaok to decide what exactly is needed from clients and why. So I'm assigning this to you, ruaok. As a sidenote, I definitely support making clientid statistics available to the public. When I wrote a last.fm plugin back in the audioscrobbler days it was very interesting to see on audioscrobbler how many users were using my plugin.

            Unassigned Unassigned
            ijabz Paul Taylor
            Votes:
            4 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:

                Version Package
                ws/3