Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <660966.1171388839619.JavaMail.jira@brutus>
Date: Tue, 13 Feb 2007 09:47:19 -0800 (PST)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSERVER-852) CreateTimestamp and ModifyTimestamp
 are sill using the startupTime of the server
In-Reply-To: <18411548.1171289886175.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Karasulu updated DIRSERVER-852:
------------------------------------

    Affects Version/s: 1.0.1
                       1.0.2
        Fix Version/s:     (was: 1.0.1)

For 1.0 it really does not make sense to update the timestamp on the subschema subentry at any time other than at startup because the schema is static.  It can only change on startup.  

The timestamp on the subschema entry is critical for client applications that 
check the timestamp to update their cached schema information.  If the 1.0.x server 
goes down for a schema update then the client must reconnect and recache this 
information.  So using the new start time is ok.  The timestamp will never change in 
1.0.x servers since the schema is static.  This is why there is nothing to be done to correct this in the 1.0 branch.

Now for 1.5.x and above we have some options.  Basically we can maintain
 timestamps (both create and modify) along with the name of the 
creator/modifier for the root schema node (ou=schema).  However 
instead of representing the time of updates to this entry we can store the 
modifyTimestamp and the modifiersName for the last change that took place to
a schema and it's entities under the ou=schema node.   This way when we 
render the schema subentry we can show the modifiersTimestamp and modifiersName from the ou=schema entry.  This will give the desired effect of alerting client 
applications to schema changes when they poll or apply persistent searches to 
the subschema entry.

 
> CreateTimestamp and ModifyTimestamp are sill using the startupTime of the server
> --------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-852
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-852
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0.2, 1.0.1
>            Reporter: Emmanuel Lecharny
>         Assigned To: Alex Karasulu
>             Fix For: 1.5.0
>
>
> The server still use the server starting time to feed those two fields. We should use the current time instead of this static date. 

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