Re: filter exception handling

We can do a rev2 of the filter api for SE1.1.  In the mean time, I think 
Jon's right - we should make all filtering fail-safe and just log the 
errors.

http://subetha.tigris.org/issues/show_bug.cgi?id=143

Jeff

Scott Hernandez wrote:
> Maybe we can create a hierarchy of voting for what to do in the case
> of a failure in one of the filters. In general, if one filter fails it
> seems reasonable for the next ones to continue. Right now we don't
> have any filters that require any other filters in order to process.
> We do have some that are order specific though, and this is something
> I see as more of an issue.
>
> It could be good to include the list of filters that will be applied
> to the message as context for each filter. In addition we could keep
> the state of that filter processing on the message (not run, running,
> failed-with exception). This would even let a filter apply another
> filter before it ran if it has dependencies.
>
> Just a thought.
>
> On 12/19/06, Jon Scott Stevens <jon@latchkey.com> wrote:
>   
>> I'm starting to think that our handling of exceptions in filters
>> should be done better/differently so that if one does fail, the
>> filter should just be ignored and the message sent through the rest
>> of the filters without having applied that one. comments?
>>
>> jon
>>
>> _______________________________________________
>> SubEtha Development mailing list
>> dev@subethamail.org
>> http://www.subethamail.org/se/list/dev
>> http://www.subethamail.org/se/archive_msg.jsp?msgId=11433
>>
>>     
> _______________________________________________
> SubEtha Development mailing list
> dev@subethamail.org
> http://www.subethamail.org/se/list/dev
> http://www.subethamail.org/se/archive_msg.jsp?msgId=11437  	
>