What I found in my tests before was that if I wrote the results to screen (pulling 50,000+ users), it would normally die somewhere around 35-42,000 in. If instead I wrote it to memory and then when it was done to disk I didn't have the same problem. Basically, for me, the http chunk of code I was using was doing some type of timeout due to waiting for things to get written to screen.
Other things to look at may be turning compression on or a timeout value. On Wed, Nov 5, 2008 at 11:44 AM, Leo <[EMAIL PROTECTED]> wrote: > > The reporting API is not downloading the complete set of results. > Anyone have any ideas on why the results are being truncated? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
