Results from the Search API should be delayed only by a few seconds
during normal operations. If there's some operational issue, search
can get behind, but this should be fairly rare.
The lowest latency API is the Streaming API. Results are often
available here before they are published onto timelines, and generally
before Search. But, we're talking by hundreds of milliseconds or low
seconds. This shouldn't matter for most applications.
On Thu, May 13, 2010 at 11:18 PM, Amit <saksena...@gmail.com> wrote:
> I am developing an application where i want to get twitter updates
> (follow-ups, tweets etc.) based on keywords straightaway into my
> application. I am using twitter4j for that purpose. The problem is
> that the search results are quite outdated as compared to the ones
> gotten through twitter directly.
> Is it a restriction imposed by twitter?
> In case it is, if there is any other API to resolve the issue or some
> customization sort of paid service provide by twitter or whatever the
> solution can be. Please respond.