API v3

[Fuyukai]

So I'm gonna be making a v3 to fix some issues v2 has (notably the region issues and the comp/qp split).

(No, I'm not retiring v2 (yet)).

I'm looking on opinions on what to split and what to unify:

• Comp and quickplay together (i.e {"competitive": ..., "quickplay": ...})
• Heroes and other stats together

Basically, if it should be a giant JSON blob (easier) or multiple routes (pls senpai nginx can only take so much on an Atom).

[Fuyukai]

Oh yeah, this also means all 3 regions and 3 platforms will be available in one request, as well as taking shorter time due to fetching all regions in parallel.

[andrewzah]

So v3 will keep the new competitive: true field? Makes sense to cut down on the routes.

[Js41637]

I'd assume it will return both quickplay and competitive stats in the one request (if available) and return all hero stats on a /heroes route.

Regions (and platforms) make things a lot harder. That's up to 5 requests for a single user to try and find their location not to mention some users are on multiple regions.

[ifonefox]

nginx can only take so much on an Atom

You're self-hosting this on a computer with an Atom Processor?

[Fuyukai]

eyes@veriny /v/w/owapi.net$ cat /proc/cpuinfo | grep "model name"
model name  : Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz
model name  : Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz
model name  : Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz
model name  : Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz

[RomainPln]

I agree all heroes stats together would help avoid 429 warnings.

[andrewzah]

When is v3 going to be merged in?

[Fuyukai]

soontm

[andrewzah]

I'm not sure how I can contribute to v3, but if there's something I can do just let me know.

[Fuyukai]

Well, I'm going to fix platforms and merge it to master tonight, then deploy it, so I need testers.