abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James M Snell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ABDERA-17) Simplify ParseFilter, Remove Text Filter
Date Tue, 27 May 2008 17:10:02 GMT

     [ https://issues.apache.org/jira/browse/ABDERA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

James M Snell resolved ABDERA-17.

    Resolution: Won't Fix

No longer a priority. The current parse filter stuff works fine

> Simplify ParseFilter, Remove Text Filter
> ----------------------------------------
>                 Key: ABDERA-17
>                 URL: https://issues.apache.org/jira/browse/ABDERA-17
>             Project: Abdera
>          Issue Type: Improvement
>         Environment: All
>            Reporter: James M Snell
>            Assignee: James M Snell
>            Priority: Trivial
> The Parse Filter and Text Filter stuff currently in Abdera has never quite been fully
fleshed out.  The Parse Filter is primarily useful as a means of filtering out parse events
we don't care about in order to reduce the memory footprint of a parse.  The Text Filter was
intended to provide a means of parse-time, policy based filtering of feed content. I'm not
aware of anyone actually using the Text Filter and it's implementation leaves a lot to be
desired performance wise.  I'd like to pull the Text Filter stuff back out and simplify the
Parse Filter even further, including a simplification of the parser implementation so that
filtering is done using a Stax filter rather than if statements in the FOMBuilder.  Doing
so should result in a more streamlined impl.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message