http://api.stackoverflow.com/1.1/usage/methods/questions-by-ids

What is the motivation for building api.stackoverflow.com in a manner that accepts multiple IDs in a resource call?

For example, I can use /questions/123/ to return the question record number 123, or I can use questions/123;124/ to simultaneously return question record numbers 123 and 124.

I like the concept, because it allows me to mimic the functionality of a query like SELECT * FROM SOME TABLE WHERE ID IN (123, 124);. But I would like to know what specific functionality or requirement a vectorized call fulfills.

I'm having a difficult time imagining a use for a vectorized call that cannot be fulfilled by a /questions? call.

Is it a multi-select from a list view?

Thanks!

http://api.stackoverflow.com/1.1/usage/methods/questions-by-ids

What is the motivation for building api.stackoverflow.com in a manner that accepts multiple IDs in a resource call?

For example, I can use /questions/123/ to return the question record number 123, or I can use questions/123;124/ to simultaneously return question record numbers 123 and 124.

I like the concept, because it allows me to mimic the functionality of a query like SELECT * FROM SOME TABLE WHERE ID IN (123, 124);. But I would like to know what specific functionality or requirement a vectorized call fulfills.

I'm having a difficult time imagining a use for a vectorized call that cannot be fulfilled by a /questions? call.

Is it a multi-select from a list view?