I am trying to make my app work with as little maintenance as possible, but also be as efficient as possible. Hence I would really like to batch up the ids I am requesting into a vector and get them with one call to the API.
However Kevin Montrose sates that the maximum number of parameters isn't in the specs because:
This isn't spec'd in the API because we'll change it whenever we please - for one, .NET 4 knocks that up iirc - and relying on it isn't supported.
So in other words I can only be sure that one id parameter will work?
Wouldn't it make sense to have a function that can be used to get the max query length or defining a value that it won't drop below for that version of the api?
It could also be good to have it defined as to what makes up the path. code poet suggests (bolding mine):
this test shows that ~290 is the max path including protocol but it seems to waver quite a bit so I am guessing that urlencoding of the semicolons is being counted on the other end.