directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Created: (DIR-202) Double modification on a modify ?
Date Fri, 02 Feb 2007 23:38:05 GMT
Double modification on a modify ?
---------------------------------

                 Key: DIR-202
                 URL: https://issues.apache.org/jira/browse/DIR-202
             Project: Directory
          Issue Type: Improvement
            Reporter: Emmanuel Lecharny
         Assigned To: Alex Karasulu


We have had a convo with alex about the OperationalService. I saw that when doing a modification
on an entry, we first call the next interceptor (and this will modify the entry on the backend),
then we add two new attributes (modifiers name and date) and store again the data into the
backend. This does not seems to be very efficient, but we don't remember the reason why it's
done like that ...

Here is the convo

elecharny in OperationalService
akarasulu yep
elecharny when doing a modify,
akarasulu ahha
elecharny you first call the next interceptor, then you update the nexus with the entry with
elecharny two new attributes
elecharny why don't you add the attrs into the entry and then call the netx interceptors ?
akarasulu hmmm I had some reason for this
elecharny this is a simple modify instead of two
akarasulu don't remember
akarasulu yeah yeah I see what you mean
akarasulu can't remember now
elecharny this seems to cost the double
akarasulu yes it does
akarasulu can you put this in JIRA
elecharny yeah
akarasulu just past this info
akarasulu from IRC

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


Mime
View raw message