Once i get the access token, how long can i retain i use it for ? So that i
need not ask the user to do the whole process again ? Is it that once in a
lifetime ?
Ronak Kumar Samantray
Hyderabad
Mobile : +91-9347290267
040-66933916
On Tue, Sep 14, 2010 at 2:05 AM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:
> Correct, you would still need to ask the user to go to a specific web page,
> where they will be asked to authorize your application and then be presented
> with a PIN code that they would enter in your application.
>
> Taylor
>
> On Mon, Sep 13, 2010 at 1:32 PM, Ronak Kumar Samantray <
> ronak....@gmail.com> wrote:
>
>> In the OOB flow also i need to redirect the user to an URL isnt it
>> where he needs to key-in a PIN code ? Or am i missing something ?
>>
>> Thanks
>> Ronak
>> --
>>
>> Ronak Kumar Samantray
>> Hyderabad
>>
>> Mobile : +91-9347290267
>> 040-66933916
>>
>>
>> On Tue, Sep 14, 2010 at 1:59 AM, Taylor Singletary <
>> taylorsinglet...@twitter.com> wrote:
>>
>>> Some mobile clients opt to use a form of OAuth called xAuth for
>>> authenticating users without the web-page-song-and-dance. You can find out
>>> more about xAuth at http://dev.twitter.com/pages/xauth and can request
>>> permissions to utilize it by sending a detailed note to a...@twitter.com--
>>> it is unlikely whether you'll receive authorization to use xAuth within
>>> 20 hours (it generally takes 3 or more days). Otherwise, you can still
>>> direct users through the "out of band" OAuth flow.
>>>
>>> Thanks,
>>> Taylor
>>>
>>> On Mon, Sep 13, 2010 at 12:29 PM, ronak <ronak....@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am developing a client application (not a web application). I am
>>>> able to get the token and the token secret. Now how do i authorize the
>>>> user ? Because for authorization i see the documentation asking me to
>>>> redirect the user to a particular web-location !! How can i achieve
>>>> this using a client-app ?
>>>>
>>>> Please help me out. I have to hit a delivery date in another 20 hours :
>>>> (
>>>>
>>>> Thanks
>>>> Ronak
>>>>
>>>> --
>>>> 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?hl=en
>>>>
>>>
>>> --
>>> 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?hl=en
>>>
>>
>> --
>> 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?hl=en
>>
>
> --
> 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?hl=en
>
--
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?hl=en
