I want the API method to "return the full social graph in as few API
calls as possible."

If your system can return up to X ids in one call without doing a 502
freak-out, then continue to do so. For social graphs with X+n ids, we
can use cursors.

On Jan 4, 6:07 pm, Wilhelm Bierbaum <wilh...@twitter.com> wrote:
> Can everyone contribute their use case for this API method? I'm trying
> to fully understand the deficiencies of the cursor approach.
> Please don't include that cursors are slow or that they are charged
> against the rate limit, as those are known issues.
> Thanks.

Reply via email to