[pLog-svn] r6088 - plog/branches/lifetype-1.2/class/security

[Jon Daley]

On Thu, 29 Nov 2007, Mark Wu wrote:
> Actually, the situation won't happened in our scenario.
>
> We don't have the mechanism to tell the next pipeline filter that the
> previous one is invalid, and you need to treat the comment as spam and train
> it again.
>
> So, even we run again all filters again, the Bayesian filter still treat the
> comment  as a"non-spam" comment

Isn't that what this is for?

$previouslyRejected = $this->_pipelineRequest->getRejectedState();


> But, another scenario may happened:
>
> If the Bayesian filter caught it as a spam, but his auhtimage is wrong. At
> that time, the comment already add to database.
> That's why some people complain to me the auhtimage fails when comment
> marked as spam.
 	Yes, I see.  I wonder what there is to do about that.  I guess the 
auth image plugin could check if previously rejected, and remove the 
comment from the database if the auth image is wrong.


> Even so, we still need to run all filters once, not twice.
 	I am working on a solution.  It isn't as pretty as I thought it 
would be, so I'll check it in when I am done and see what you think.