Hello,
imho it makes little sense to cache the regularly occurring error responses
from the twitter API servers. A 502 Bad Gateway status would mean, for example,
that the same (usually transient) error is returned until the cache-timeout
expires.
Therefore, the attached patch only caches successful requests.
Alternatively one could also cache responses with status codes in the 400 since
those usually are not as transient as the 500s. (E.g., a 404 Not Found status
will only rarely disappear as a result to a repeated identical request).
thx
-d
Original issue reported on code.google.com by yae...@gmail.com on 30 Sep 2010 at 10:02
Original issue reported on code.google.com by
yae...@gmail.com
on 30 Sep 2010 at 10:02Attachments: