Hello Willy.

There is one feature that would really be great.
Some kind of BOINCstats API...

Let me explain. We only have the stats of our team/members in our database, so information about the position in the rankings is missing.

It would be great to have an url to get world positions, e.g. like get_worldposition_user.php?cpid=...&pr=...
which just returns the number.
The same for the team with teamid.

Do you think this is thinkable or would the traffic be too much for you?

would something similar to the XML pages (not the DB export) currently available for some project pages work?
because an API is something completely different (althought i know what you mean, a more appropriate term is "web RPC" but that's just symentecs )

if getting an XML formatted reply to a GET request would do, then i think it wouldn't be too hard to implement, and the traffic would be much less than HTML scraping (parsing HTML pages, XML is better for data exchange), but obviously willy would have to comment, it's his server and spare-time after all



there is mention of this in FAQ #17:

the extra stress is caused by HTML scraping, and the "special method", i assume, is XML based

I don't know if this has everything you are looking for, but the Berkeley stats page has a description of some RPCs you can make as well as some xml files you can download to generate your own stats if you would like. I haven't used it much myself, but it seems to include aggregate data across all projects (for world rankings, etc) as well as project specific information. The data is hosted at http://boinc.netsoft-online.com/.

I hope it helps!

smith

We already have our own stats, but only for our team and not for the whole world
XMLs with exported world-rankings would be great.
Perahps one xml for every team and project (and overall) including the members ids and world rankings.
Same for teams of a project.

well, it probably wouldn't be an exported XML file that you download as such, but just an XML page which is generated based on the URL in the GET request (much like the web RPC scheme for projects). I think that would be more efficient than exported XML files (i could be wrong, it would depend on how many requests were made for the same content before it changed, willy would have to comment, in short there's more overhead with exporting XMLs but if lots of requests are made for a set of exports (in one state, before they're updated the next time) then it would probably be more efficient to generate them once and serve them as static files, rather than having to generate them for each request (unless server-caching is used), as you can see, it gets quite complex rather quickly)