이 사이트는 자바스크립트를 사용합니다.
브라우저에서 자바스크립트를 활성화 해주십시오.
라이브
PTR
10.2.7
PTR
10.2.6
베타
Wowhead API?
답글 달기
보드 인덱스로 돌아가기
571215
의 게시글
This post was from a user who has deleted their account.
Wanderingfox
의 게시글
Eventually... It's pretty low on the totem pole of 'stuff to get done' though iirc.
Incendium
의 게시글
You mean something like
this
?
Wanderingfox
의 게시글
That's not really an API and it doesn't cover the entirety of Wowhead's data :P
Gnub
의 게시글
That's not really an API and it doesn't cover the entirety of Wowhead's data :P
It actually
pretty much is
.
I wonder however, what data doesn't it cover, that is on Wowhead? :P
Wanderingfox
의 게시글
Except that it's not fully implemented. It's provided as is, and only works on a small subset of links, and even then it responds erratically. There's no documentation, no support, and is limited in it's use as far as developing actual applications are concerned (there's no way to get an xml formatted list from a search query without transforming the html output for example).
edit:
To answer your second question, it only works with items, and even then only specific items. It won't find multiple items with the same name, items that contain random enchant properties (like the JC crafted rings), or return an xml result when multiple items match the query given (it returns only the first). It also does not return any of the comment information. Lastly, it does not work on: quests, achievements, spells, or profiles at all.
571215
의 게시글
This post was from a user who has deleted their account.
Gnub
의 게시글
I see, Wanderingfox. Good catch.
pelf
의 게시글
The resulting response to this question is always that they're worried about making it easier than it already is* for people to scrape Wowhead's database.
*WOWDB
Jakobud
의 게시글
There are lots of threads about any type of Wowhead API access. A client of mine has recently started figuring out a similar approach to designing an API, so I posted the question on Stackoverflow and got some good answers and suggestions:
http://stackoverflow.com/questions/4425877/design-an-api-for-a-web-service-without-selling-the-farm/4426065#4426065
If you were to provide a wowhead api, here are some key points:
Don't just allow anyone with an email address to use the API. Put a signup process in place for it. This way you will know who is signing up for it and what they intend to do with it.
Assign API keys to people who want to use it. That way, you can see who is pulling what from the database.
Throttle usage - Since you know who is pulling data, you can also limit the number of queries per hour or something like that.
With assigned API keys you will be able to easily tell if someone is mining the database and cut them off
Put a formal license agreement or TOS in place that requires anyone who uses to API to conform to certain rules. For example, perhaps any webpage that displays information from the wowhead API is required to have a wowhead logo or image on it with links back to wowhead.com so that it is obvious where the data is coming from. Anyone who does not conform to the rules has their API key revoked. I'm not sure how hard this would be to police.
There are a lot of web services out there that successfully deploy API's to developers without giving up all of their valuable database information. Just gotta figure out how everyone else does it and follow along.
Erorus
의 게시글
Jakobud: and after all that work making a formal API, how does that make Wowhead any more money?
Wowhead's dev team has limited resources (as do all). They have 100 things on their to-do list, and 75 of those can make the site better, which increases page hits, which pleases advertisers, which makes more money. 25 of those things are neat things, but probably don't increase page hits. So if you're on a dev team, and you can make neat stuff that brings in bucks or neat stuff that doesn't, doncha think they'll make neat stuff that keeps them employed?
If you want a proper API, along with your "here's how" you should include a "here's why."
답글 달기
로그인이 되어있지 않습니다. 답글을 달려면
로그인
하거나, 계정이 없다면
회원가입
을 해 주세요.