Thanks James. But for this i need to look into the Twitter account constantly right! I have to write a loop which is running all the time and looking for the Twitter users account for the updates. If this is the case, i was wondering will it be a problem for the application performance.
Thanks, Muni. On Tue, Nov 11, 2008 at 8:52 PM, fastest963 <[EMAIL PROTECTED]> wrote: > > You would have to use the > http://apiwiki.twitter.com/REST+API+Documentation#usertimeline > You can do either two things... > > With Database: > Store the id of any ads you enter after entering (see later) > Fetch the contents of > http://twitter.com/statuses/user_timeline.xml?since_id={last<http://twitter.com/statuses/user_timeline.xml?since_id=%7Blast>id > of ad} > Then get the count of what is in the xml file. If its = or greater > than the ad "frequency" then you need to push an ad (see later) > Ex: If freq is 1 of 3, and the count of posts in the xml is 2 or more, > then you need to push an ad. > > Without Database: > Fetch the contents of > http://twitter.com/statuses/user_timeline.xml?count={frequency}<http://twitter.com/statuses/user_timeline.xml?count=%7Bfrequency%7D> > Then check each post to see if any contain your ads, if not, then you > need to push an ad (see later) > Ex: If freq is 1 of 3, then your count is 3, if the XML file contains > a "tweet" with your ad then you need to wait, if it doesn't then you > need to push an ad > > > Pushing(posting) an ad: > http://twitter.com/statuses/update.xml?status={insert<http://twitter.com/statuses/update.xml?status=%7Binsert>ad > code here} > > > (note: each of the above API references can either be xml or json, its > up to you) > > I hope that helps! > -James Hartig > -- Munendra Chevuru, Associate Software Engineer, @09884303520
