World_id on events.json required parameter?

World_id on events.json required parameter?

in API Development

Posted by: Ruhrpottpatriot.7293

Ruhrpottpatriot.7293

Yeah, pretty much that what the title says.

Currently it is possible to get all events on all servers, which can take a long time, since there are 51 worlds each with about 1500 events which results in over 76000(!) possible events which will take a long time to get.

Making the world_id a required parameter will make the time required a lot less.

Opinions?

Administrator of GW2.NET: GitHub , Forum , NuGet

World_id on events.json required parameter?

in API Development

Posted by: DarkSpirit.7046

DarkSpirit.7046

I don’t see how making world_id a required parameter would be better. Right now you have a choice of listing all of the events or filtering them through world_id, map_id, and/or event_id. This means you can choose to have the result filtered for you or not.

Having choices is good.

World_id on events.json required parameter?

in API Development

Posted by: The Talcmaster.7391

The Talcmaster.7391

if you don’t want all data, then make sure to include world_id. If you made that a requirement, it would be much slower for people who need to pull in data from all worlds. It would be a significant downgrade.

Fort Aspenwood – [fury], [SAO], [NICE]
Fun on someone else’s schedule is not fun

World_id on events.json required parameter?

in API Development

Posted by: rodadams.5963

rodadams.5963

Also remember that connection/request setup and teardown is generally the most expensive thing, so one request for all ~76k events is likely cheaper than 2 requests for ~1500 each.