The web interfaces take several parameter types. Some are obvious, "cpid" for example, others, not so. Is there a list of what they all are and how to obtain them?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

It's described on the wiki: [trac]wiki:WebRpc[/trac]

Yes, okay, but that is not what I really mean. Sure, (using account-key as an example), if I know the users email address and their password, I can query for the key. But I don't, and would consider it wrong that I did, (I know their e-mail of course).

Yes, a computer savvy user could get their own account-key then send me that to use, but most team members aren't that good. I had kind of assumed that somewhere in the pages the user can see, they would be able to obtain their key and copy/paste it into a form I can give them.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Yes, okay, but that is not what I really mean. Sure, (using account-key as an example), if I know the users email address and their password, I can query for the key. But I don't, and would consider it wrong that I did, (I know their e-mail of course).

Speaking of the account key only, you only need the email address. Not the password. Or else you wouldn't need the account key in the first place, as you'd be able to log into the account, using the email address and password (on some projects, the account name and password)

Example given: request account key of the BOINC forums.

The email address should be in the database. You can't request someone else's account key and send it to yourself. If you fill in your email address, you get your account key.

---

Yes, okay, but that is not what I really mean. Sure, (using account-key as an example), if I know the users email address and their password, I can query for the key. But I don't, and would consider it wrong that I did, (I know their e-mail of course).

Yes, a computer savvy user could get their own account-key then send me that to use, but most team members aren't that good. I had kind of assumed that somewhere in the pages the user can see, they would be able to obtain their key and copy/paste it into a form I can give them.

It's worse if they give you their account key than if they give you their password. Users can change their password, but not the account key, and both give you the same login possibilities.

Hmmm, I wanted to use the show_user RPC to provide my team with "per machine" stats as they have been asking for.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

As long as you don't need cross project stats, you can access everything you need through the Account numbers which are listed in the links under the "Name" column on the team page.

If you need it cross-project, I wouldn't know any way to get it from the project pages, you would need the exported stats in that case.

The parameter names are not used consistent through the web pages, w.g. some use teamid and some need team_id instead.

Two pages accept "&format=xml" (team_lookup.php and show_user.php). As all others don't have the XML option for such a long time now, I doubt that they will ever have it.

You can go through the PHP code of the pages you want to scan and look for the get_int()/get_str() block, which is always close to the top of the source. They will tell you which optional parameters a page knows.


p.s.: I might have misunderstood - if you plan to use RPC, not the web interface, my reply would be pointless - sorry in that case.

Two pages accept "&format=xml" (team_lookup.php and show_user.php). As all others don't have the XML option for such a long time now, I doubt that they will ever have it.

show_user.php?format=xml doesn't list hosts unless you also pass the user's account key, which is the equivalent of his password.

yep, that's what I mean, hosts_user.php (with userid parameter) has the information but is missing the option for XML output - harder to parse.

The problem with the exported stats is that even for small projects, the files are HUGE, and require a lot of processing where 99% of the content is useless, (other teams). If you run a team that has crunchers in most of the projects, then downloading the 3-4 stats files from each of the projects possibly several times a day is a real problem.

harder to parse.

That is why many teams still use screen scraper technology. We use RPC where we can, but there comes a limit. Screen scrapers are inefficient, and a pain to maintain, but with limited resources, what else can you do?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

yep, that's what I mean, hosts_user.php (with userid parameter) has the information but is missing the option for XML output - harder to parse.

If hosts_user.php with userid parameter gives you the hosts, even if you aren't the owner, I see no reason for the XML version not to do the same.

---

... If hosts_user.php with userid parameter gives you the hosts, even if you aren't the owner, I see no reason for the XML version not to do the same.

If there was an XML version, it sure would do the same.

But as noted above, only team_lookup.php and show_user.php have an XML option.

I don't have the latest code snapshot here but I tried the XML option on hosts_user.php and it did nothing.

A wap version would be easy to parse as well, but that only exists for userw.php