Pat, is it just you maintaining the public API now?
Nope, I did a bunch of work on a first version of the /v2 commerce APIs (& the quaggan API because quaaaaaaaaaaaaaaaaaggans). There’s another programmer working on that stuff now fortunately.
Fixed on dev. Don’t have an ETA on when it’ll go out to Live just yet.
My best guess is that listings are (lazily) loaded in parallel, so the order would be undefined. For practical purposes, that means that the list goes from listings with few offers to listings with lots of offers.
No idea if that’s how it really works.
Yup, we make a bunch of async requests for the data and simply assemble it in the order it returns.
Now, as for object-vs-array:
Shoving results onto the end of an array as we get them back is easy and lets you do nice things like check the length of the array to see how many items you got back. It also means you can use useful array functionality like (JS examples) .some(), .every(), .reduce(), etc w/o first having to jump through a bunch of hoops.
Constant-time lookups of a specific data ID doesn’t feel like a worthwhile trade-off for an API that is generally intended to provide bulk data, and if you did want that you could ask the API for data for the specific ID you cared about.
I’m open to sorting by ID once we have all the data back if you’d find it useful, I don’t think it would help programmatic usage much but does make the data nicer to look at.
/v2/commerce/prices is what we show in search results on the TP and totally usable for places where absolutely up-to-the-minute data isn’t necessary.
/v2/commerce/listings is closer to being live data, but is also more expensive for us to retrieve. It may end up getting a longer cache time on it to avoid problems on the backend.
Unsure, I wasn’t involved in the original genesis of the /v2 APIs and only tangentially involved in /v1.
Worth looking at, but I suspect there’s some privacy concerns there until we get authenticated APIs in place.
Oh, hah. I totally misread that as X-Page-Total and X-Page-Size.
It’s because the commerce APIs take a different code path from the rest of the /v2 APIs. We’ll take a look at it.
I signed up with Starfleet Dental [SFD] on Maguuma, I hear they’re very professional.
A few, most of /v2 is just exposing existing /v1 data in a cleaner & more useful way. We’ll keep adding new APIs as they make sense to it, but don’t expect seismic shifts in the data you can get out.
Still broken for me. :/ Does it take some time for API changes to roll out for everyone?
Looks good to me, can you provide some details?
This was deployed a few days ago, would love to know if the bug’s still happening.
Are you guys still seeing this regularly? I still can’t reproduce it but haven’t forgotten about you
The blog will be coming back, it was an unfortunate schedule casualty.
Thanks for the info, we were just talking about a better way to make this info available yesterday. That experience should be better.
Looked into this a bit, I’m not seeing these issues in Firefox/Chrome/IE10.
Since I’m at home I’m running beta versions of Firefox & Chrome though, I’ll take a look tomorrow when I get in & see if I can reproduce this.
Opera’s being wonky is a known thing, it’s not a priority because we get so little Opera traffic.
IE8+ does CORS fine, you’ll just need to use XDR instead of XHR for IE 8 & 9. We do it regularly & it works great.
JSONP is an elegant hack… but it’s still a hack.
Yeah, somebody forgot to update the alias. Should be fixed before too long.
Does logging into account.guildwars2.com work? The forums login isn’t doing anything special. Does Chrome work?
Might be worth clearing your cache & giving it another go?
Have you tried going to account.guildwars2.com & making sure you’re logged-out there? Sometimes the forums/account site get into a fight over whether or not a session is valid & fun things happen.
Bad deploy caused some issues for the french version of the site, should be fixed now but if you’re still seeing issues post the bad URLs please.
Thanks for the reports. We know about the issue and will fix it once higher priority issues are taken care of.
Sorry about that!
He’s redirecting to the live TP site. It’s already in our whitelist.
Those aren’t attempts, those are successful logins using your credentials.
To stop them I recommend immediately changing your password to a new one that is unique to GW2. You should also stop using that password anywhere else.
Strings got shuffled around and that one got missed, sorry folks. Should be fixed in a bit.