> The problem is that I'm designing an app for cases where twitter.com > is inaccessible by the user because of regional bandwidth restrictions > - so oauth would not work. The api mentions that "Session cookies and > parameter-based login are known to work but are not officially > supported." so am hoping that someone here can point me in the right > direction on that.
I'm assuming your service only makes intermittent access to Twitter. However, this is actually an optimum situation for OAuth -- you only need to cache the access token, which (hopefully) will last for _A_SUFFICIENTLY_LONG_TIME_. You do not need to keep hitting twitter.com to keep the access token alive, only when the token finally expires (which may be indefinite -- this is TBD). If you conceive of the access token as a special form of cookie, you'll see this still works. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- If you have integrity, nothing else matters. -- Alan Simpson ---------------
