Re: Ratings and throttling

>
> The only thing I can think of offhand is that you can get recording
> ratings via release requests and via recording browse requests, e.g. by
> artist. So if you have release tags and artist tags you may be able to
> get ratings for all recordings at once (or, in the case of browse
> requests, up to 100 at once via the limit parameter).
>

If I did it by release, then I'd need to do a separate query for each
release, right?  I guess that would be faster than one request per
recording, but if I have 600 albums, then that would take about 10
minutes.  Still a bit slow.  And, if a release had more than 25 recordings,
then it would get truncated.

Doing a browse request by artist I think would have a similar problem.  If
I have 300 artists, that's 300 requests, each of which may have several
100-recording pages, so that might take just as long.

And since in both of these cases, I'm getting back lots of data that I
don't care about (recordings that I don't own), it's probably not too nice
to the server.

Thanks for the info and ideas, though.  I really hope somebody implements
the feature request that Ulrich linked to.  It would make eveything nice
and clean.  It doesn't sound like too difficult a job.  I'd possibly
volunteer myself if I knew Python :)

So, it looks like I might have to resort to using the user rating web page
and scraping the HTML (as the feature request mentions), and just hope that
the format doesn't change :(

-Joe

_______________________________________________
MusicBrainz-devel mailing list
[email protected]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-devel