Yes, I understand that the page # is the page # and that I have access
to about 150 of those, and I am processing the json file properly. I
will double check the data types I'm using. Looking through a json
response, the twitter api thinks I am entering negative dates (for
since) (not the case).
On Apr 21, 10:34 am, Nick Arnett <nick.arn...@gmail.com> wrote:
> On Tue, Apr 21, 2009 at 8:41 AM, Joseph <northwest...@gmail.com> wrote:
>
> > page (number of
> > pages returned per search).
>
> I'm not sure if you meant what you wrote here, but page is the page number
> of the search results for one query, not the number of pages returned per
> search. In other words, you'd iterate through the available pages to get
> all of the available results.
>
> However, the search API also returns a URL for the next result page
> ("next_page"), so you don't have to make your own iterator unless you wish
> to skip some results pages for some reason.
>
> Nick
