Closed GoogleCodeExporter closed 9 years ago
I haven't delved into the code too far. But I don't think it is actually
authenticating the second time. The default cache time is 1 minute. I think
if the code is re-executed within that timeframe, it will pull from its cache
instead of re-authenticating. Have you tried waiting 5-10 minutes and trying
again with the wrong password?
Original comment by gaur...@gmail.com
on 28 Jul 2010 at 8:18
should we automatically invalidate the cache for the twitter id if an
authentication error happens?
My gut is to say no to this as all caching is local so it's not like your
getting someone else's data.
Original comment by bear42
on 29 Jul 2010 at 9:53
Marking this as invalid. The data being returned is cached data so the
password being wrong isn't even considered.
A more accurate Issue would be to say that the cached data should be
invalidated if SetCredentials() is called.
Original comment by bear42
on 18 Aug 2010 at 7:53
Original issue reported on code.google.com by
selva4...@gmail.com
on 3 Oct 2009 at 11:24