Closed (fixed)
Project:
Mollom
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Sep 2010 at 21:32 UTC
Updated:
24 Apr 2014 at 17:13 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sunThis is how I think it should work. mollom() already handles everything. Of course, the recursion is ugly, but I think it avoids to duplicate a lot of code and we get the identical fallback server handling for mollom.getServerList in the end.
Comment #2
dries commentedHere is an alternative -- not tested, just prototype code but I think it might work.
The advantage is that is keeps
mollom()clean.mollom()is already quite complex and the proposed patch in #1 makes it even harder to grok.Comment #3
sunIt is not really the error code that should make a difference. If we do not want to go with recursive mollom() attempt, then we'd have to do it like in attached patch. I hope the code comments explain it.
Comment #5
sund'oh. ;)
Comment #7
dries commentedIf we get a MOLLOM_REFRESH it is better to move to the next server instead of aborting, IMO.
If we get an error, we need to try the next server in the list. The error might be a network error (i.e. timeout because the server is down) so we should try the next server.
Comment #8
sunPerhaps this makes us happy? :)
Comment #9
dries commentedCertainly makes me happy. :)
Committed to CVS HEAD.
Comment #10
sunSame for D6, will test manually.
Comment #11
sunThanks for reporting, reviewing, and testing! Committed to D6.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.