Re: Limits on request length - Brad Fitzpatrick - com.googlegroups.social-graph-api

2 messages in com.googlegroups.social-graph-apiRe: Limits on request length

From	Sent On	Attachments
Martin Atkins	24 Jun 2008 13:26
Brad Fitzpatrick	24 Jun 2008 14:01

Subject:	Re: Limits on request length
From:	Brad Fitzpatrick (brad...@google.com)
Date:	06/24/2008 02:01:57 PM
List:	com.googlegroups.social-graph-api

If you specify too much stuff, you should never get an error message: not invalid and not unavailable. Both would be the SGAPI's fault.

At least one of those errors mean that things took too long to calculate. I've been working on making fme=1 lookups a lot faster which will help with that. In the meantime, restrict yourself to fewer queries at once when using fme.

But the other error is probably a bug. I'll look into it.

On Tue, Jun 24, 2008 at 1:27 PM, Martin Atkins <ma...@degeneration.co.uk> wrote:

An app I'm working on is making requests to the SGAPI for a large amount of URLs. (it's following friend links, much like the "find missing links" demo does.)

In some cases I seem to be getting back either "invalid request" or "service unavailable" error responses. I've been unable to figure out exactly what triggers them, but generally for any particular request URL the same URL will be returned consistently as far as I can see.

My app batches up requests following the example of the missing links demo. I was initially capping each request to 15 URLs as that demo does, but when I found that I was still hitting errors I also put in an upper limit for how long the value of the "q" argument can get, which is currently set to 600 since this seems to be a sweet spot that allows my fetches to complete most of the time.

Is there any upper limit on either the number of URLs or the length of the query string for a particular request?