World_id on events.json required parameter?
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.
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
Fun on someone else’s schedule is not fun
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.