Hey Alex,

We have looked into the search api and are currently rewriting the
application.
We will test it in a couple hours and I'm pretty sure it will be what
we need.
There are just have a few little issues to overcome first.

Thanks for the tip and help!

-Lee



On Nov 19, 11:57 am, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Sure does.  You might check out the Search API.  You can retrieve
> @replies that way as well, and in higher volume.
>
>
>
> On Wed, Nov 19, 2008 at 09:51, ThatLeeGuy <[EMAIL PROTECTED]> wrote:
>
> > Hey Alex,
>
> > The application retrieves all of the @replies to a single specific
> > user usinghttp://twitter.com/statuses/replies.xmland stores them to
> > a database.
>
> > As there is a limit of the last 20 @replies and I do not know really
> > how much traffic I am requesting the replies.xml on every visit.
> > It could be as high as 2500 requests an hour or as few as 200, but I
> > think it will be a very brief period of high traffic with a plateau
> > and decline within 60 hours to a sustained level of 500/hr.
>
> > If there was a way to retrieve more than the last 20 @replies, say 500
> > or so, I could easily step this frequency down using caching and not
> > worry about missing any replies.
>
> > Does that make sense?
>
> > Thanks Alex,
>
> > -Lee
>
> > On Nov 18, 10:56 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> >> > I want an website application white listed that uses an authenticated
> >> > request for past replies. Is it ok that we used a domain and ip in our
> >> > application rather than a user account?
>
> >> Just IPs, please
>
> >> > What do you need to know in the way of application details to provide
> >> > you with enough information to make a decision?
>
> >> What the application does, how often you plan to request which methods.
>
> >> > Lastly, I understand that you probably have greater issues today, how
> >> > long do you think it will be before we know if we are approved?
>
> >> Between one and three days.  I just cleared out the backlog of requests.
>
> >> --
> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

Reply via email to