You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2006/07/30 11:04:13 UTC

[jira] Created: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Entry lookup are done more than once in modify operation
--------------------------------------------------------

                 Key: DIRSERVER-683
                 URL: http://issues.apache.org/jira/browse/DIRSERVER-683
             Project: Directory ApacheDS
          Issue Type: Improvement
            Reporter: Emmanuel Lecharny
             Fix For: 1.1.0


If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.

This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.

For ApacheDS 1.1 or 2.0 ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-683:
----------------------------------------

    Fix Version/s: 2.0.0-RC1
                       (was: 2.0.0)

Moved back to 2.0.0-RC1

> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0-RC1
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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


[jira] Resolved: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-683.
-----------------------------------------

    Resolution: Fixed

Removed the useless lookups with http://svn.apache.org/viewvc?rev=949402&view=rev


> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0-RC1
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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


[jira] Updated: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-683:
------------------------------------

    Fix Version/s:     (was: 1.5.1)
                   1.5.2
         Priority: Minor  (was: Major)

> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 1.5.2
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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


[jira] Updated: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-683:
------------------------------------

    Fix Version/s:     (was: 1.5.0)
                   1.5.1

Yeah this is something we can do as part of a big cleanup.  Perhaps it's best if we push this one off until 1.5.1 or later.  However I think problems that arise are going to push us to have to do it sooner rather than later.

> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>             Fix For: 1.5.1
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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


[jira] Updated: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-683:
----------------------------------------

    Fix Version/s:     (was: 1.5.2)
                   2.0.0

PERf = 2.0

> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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


[jira] Closed: (DIRSERVER-683) Entry lookup are done more than once in modify operation

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-683.
---------------------------------------


> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0-RC1
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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