directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-677) Refactor interceptors so only one SearchRequestFilteringEnumeration is used
Date Sat, 25 Aug 2007 21:33:31 GMT


Emmanuel Lecharny updated DIRSERVER-677:

    Fix Version/s:     (was: 1.5.1)

Far too complex to be done for 1.5.1.

Postponed to 1.5.2

> Refactor interceptors so only one SearchRequestFilteringEnumeration is used
> ---------------------------------------------------------------------------
>                 Key: DIRSERVER-677
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0-RC3, 1.0-RC2, 1.0-RC1, pre-1.0
>            Reporter: Alex Karasulu
>            Priority: Trivial
>             Fix For: 1.5.2
> We need to clean up the number of nested (wrappings of) SearchResultFilteringEnumerations.
 It's best if we relocate the code that wraps Partition specific Enumerations with this into
the Nexus.  There we can add Filters to a single SearchResultFilteringEnumeration.  Right
now a few interceptors wrap 3 layers of SearchResultFilteringEnumerations.  Here are the offending
> (1) DefaultAuthorizationService
> (2) SubentryService
> (3) CollectiveAttributeService
> Creating a new SearchResultFilteringEnumeration everytime costs us about 2% total of
processing time in search operations.  We could save a total of 4% and improve the code.
> Regarding addFilter usage
> ------------------------------------------
> Note that some interceptors, these 3, need to add filters at searh construction time
rather than at interceptor service init time.  These services can use the addFilter() interface
of the SearchResultFilteringEnumeration but this interface must make sure the first prefetched
entry is evaluated otherwise the first entry will be returned even if your filter rejects

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

View raw message