please issue incremental requst,i will be thank ful> Date: Mon, 2 Feb 2009
18:03:16 -0800> From: [email protected]> To:
[email protected]> Subject: Re: user_timeline count
parameter reliability> > > Maybe we've made a terrible omission in our
documentation, but the > "count" parameter is for limiting downwards, not
upwards. If you only > want 5 statuses in a timeline rather than 20, "count" is
a-okay. But it > isn't meant for pushing up the number of statuses returned.> >
Damon C wrote:> > Twitter-folk,> >> > I would really love to decrease the
run-time on TweetStats by> > utilizing the ?count parameter on the
user_timeline method. However,> > more often than not, increasing count above
750 or so simply errors> > out or requires numerous attempts to be successful.
(I should also> > mention that the errors are the standard Twitter "over
capacity" HTML,> > as opposed to an API 503 response).> >> > Should I stop
trying to grab timeline information in one chunk and> > continue to issue
incremental (but numerous) requests with a small> > count parameter? Your
advice is appreciated.> >> > And the token "thank you" for making the vast
amount of info that is> > Twitter so readily available. :)> >> > Damon> >> >
--> > Damon P. Cortesi> > Security guy, Weekend Haxor> > tweetstats.com |
tweepsearch.com> >
_________________________________________________________________
Plug in to the MSN Tech channel for a full update on the latest gizmos that
made an impact.
http://computing.in.msn.com/
