Hi Arnaud,
I'll try it (should work i think)
the "X-FeatureRateLimit-Reset header " question had actually nothing
to do with the oauth question.
in the docs i could not find what happens if the limit is reset.
I guess after that every authenticated call will just work again
So in my mind it should be something like (proglang neutral ;-] )
get authenticate data
While not finished
{
get limit
while not limit
{
do stuff with authenticated call
get limit
}
if not finished wait until reset
}
finished
On Apr 18, 6:29 pm, Arnaud Meunier <[email protected]> wrote:
> Hey Ton,
>
> There was a similar discussion on this ML a few days ago:http://bit.ly/icFfcC
>
> We do not expire access_token (unless a user explicitly rejects you app) so
> you don't have to go through the whole OAuth dance once someone approved
> your app. Store your user's access_token and implement a session handling
> system.
>
> Arnaud / @rno <http://twitter.com/rno>
>
>
>
>
>
>
>
> On Mon, Apr 18, 2011 at 5:20 AM, ton <[email protected]> wrote:
> > Hi. I've made an app (for browser and mobile device and Desktop) It
> > works fine but every time I start the app I have to get a new
> > PINnumber from Twitter.
>
> > Is there a way to trust an application once and use the given
> > trustdata for all the subsequent uses?
> > Best rgds,
> > Ton
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
