Skip to Content
12-08-2008 @ 2:29PM
A nice idea but the whole "whenever and however" is window dressing because you're still at the mercy of the actual Blizzard Armory for the data.A lot of information isn't supplied by the game API and or would mean some very large LUA tables having to be constantly submitted.So this means, when the Armory doesn't update NEITHER DO THEY.It's a sad fact of life but there is no way around this, Blizzard is a gate keeper holding all the keys...
12-08-2008 @ 2:54PM
I have to agree - Ive done some XML parsing (using ColdFusion) of the Armory data to build myself a few nifty compare tools, but the biggest headache Ive ran into is the Armory's instability. Still, its the only way to get the character data I want, so I do my best to work around it. Ive found that caching the data locally to a temp database helps a lot, as long as you have a "force update" option for when you know the data is old. Simply timestamping the local data makes it easy to slip in some "if older then 1 hour" logic, which is often fine enough for my needs.
12-08-2008 @ 4:15PM
@Arturis You should always be caching your data when using 3rd party sources no matter the project. It is poor form to do live queries.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.