...
As far as the protocol is concerned we have some advantages and good synergy.
...
Operational
...
Attributes: revisions
We can use operational attributes to track the revision numbers of changes that took place on an entry. This allows us to use the directory itself to request version specific information. Let's for now presume we created a special revision revisions operational attribute that can only be modified by the directory. The attribute would be multivalued and would be of the INTEGER syntax. Presume revisions are just numbers representing states of the entire directory tree like in Subversion.
With the proper matchingRules we can ask the server about which entries were changed, present, or deleted using filters on this attribute as well as others.
| No Format |
|---|
attributetype ( 1.3.6.1.4.1.18060.0.4.1.2.TBD NAME 'revisions' DESC 'Revisions which have altered an entry' EQUALITY integerMatch ORDERING integerOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 NO-USER-MODIFICATION USAGE dSAOperation X-SCHEMA 'apache' ) |
Using LDAP Revision Tags
| Warning |
|---|
We must qualify what we mean by a tag since in LDAP there are tags and the concept of a tag also exists in versioning WRT snapshots. These two concepts are not related so please when discussing tags either on our mailing list or in documentation qualify them with either LDAP Revision Tag, or Changlog Snapshot Tag. |
...