This is definitely not how TwitterOAuth should be acting. You can try the
example site and it is running fine:
http://twitteroauth.labs.poseurtech.com/connect.php

Somethings to check for: Are there an for/while/etc loops in your script
that might not be functioning properly? Is it possible that there is code
somewhere that is waiting for a period of time? Have to broken down the
different parts of the OAuth flow to see if a particular part is slow? Could
just your connection to twitter.com from your server be slow?

Abraham
-------------
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.


On Sat, Sep 4, 2010 at 08:23, Corey Northcutt <corey.northc...@gmail.com>wrote:

> Yesterday I implemented Twitter oAuth on my site, using really nothing
> but a cut and paste of the example from the twitteroauth class on
> github.  It's working fine, with one hang-up-  it's incredibly slow -
> like at least 30 seconds to process the connection, even during those
> occasional instances that Twitter itself overall is running fast.  See
> here:
>
> http://www.famousquotesabout.com/widget-apps/
>
> I've noticed that other Twitter web apps I've used seem to be able to
> process the whole interaction, callback and all, in just a couple
> seconds.  I really have no idea what could cause such a delay, and I'm
> again using really nothing but the bare example code.  Has anyone else
> seen similar issues?
>
> --
> 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

Reply via email to