When Twitter bridge encounters a 403 (rate limit) err, drop the notice

instead of requeuing.
This commit is contained in:
Zach Copley 2010-01-13 19:15:54 +00:00
parent 116c5f6839
commit 43170b3d18

View File

@ -269,19 +269,23 @@ function process_error($e, $flink, $notice)
common_log(LOG_WARNING, $logmsg); common_log(LOG_WARNING, $logmsg);
if ($code == 401) { switch($code) {
case 401:
// Probably a revoked or otherwise bad access token - nuke! // Probably a revoked or otherwise bad access token - nuke!
remove_twitter_link($flink); remove_twitter_link($flink);
return true; return true;
break;
} else { case 403:
// User has exceeder her rate limit -- toss the notice
return true;
break;
default:
// For every other case, it's probably some flakiness so try // For every other case, it's probably some flakiness so try
// sending the notice again later (requeue). // sending the notice again later (requeue).
return false; return false;
break;
} }
} }