[How to batch up multiple id requests to maximize economy and still avoid (400) Bad Request][1] [closed]


<pre>
closed as noise or pointless by Kevin Montrose♦ Aug 16 at 23:15
This question does not add anything useful; having it present on the site is actively
 harmful because it distracts from other more useful questions.
</pre>

At the time, the API was killing requests with longer than an undefined path length.

see: http://stackapps.com/questions/619/url-length-limit-for-for-requests-taking-vectorised-ids-answers-id-question


In the spirit helping people maximize economy of requests while working around this limitation, which has subsequently been relaxed, I took the time to clearly define the problem and provide  detailed guidance and code.

When the limitation was relaxed, I updated the post, prominently stating that the problem had been fixed and provided a link to the announcement.

During a recent and, in my opinion, unwarranted, CW spree on my guidance posts, kevin closed the post listed above as 'noise or pointless'.

I think this is completely inaccurate and completely inappropriate and I take offense.

Thoughts?

  [1]: http://stackapps.com/questions/889