Delta-syncrepl is not supported yet with mirror mode.

[openldap] / doc / guide / admin / appendix-changes.sdf

diff --git a/doc/guide/admin/appendix-changes.sdf b/doc/guide/admin/appendix-changes.sdf
index e7e4f9b058dfbdf1881656841b57d7e173e3f7a3..eb075bd40c36136876f3eb9dcf84c5db2bc6f11b 100644 (file)
--- a/doc/guide/admin/appendix-changes.sdf
+++ b/doc/guide/admin/appendix-changes.sdf
@@ -1,5 +1,5 @@
 # $OpenLDAP$
-# Copyright 2007 The OpenLDAP Foundation, All Rights Reserved.
+# Copyright 2007-2008 The OpenLDAP Foundation, All Rights Reserved.
 # COPYING RESTRICTIONS APPLY, see COPYRIGHT.
 
 H1: Changes Since Previous Release
@@ -23,7 +23,13 @@ asked on the OpenLDAP mailing lists and scenarios discussed there, we have added
 * {{SECT:Tuning}}
 * {{SECT:Troubleshooting}}
 * {{SECT:Changes Since Previous Release}}
+* {{SECT:Upgrading from 2.3.x}}
+* {{SECT:Common errors encountered when using OpenLDAP Software}}
+* {{SECT:Recommended OpenLDAP Software Dependency Versions}}
+* {{SECT:Real World OpenLDAP Deployments and Examples}}
+* {{SECT:OpenLDAP Software Contributions}}
 * {{SECT:Configuration File Examples}}
+* {{SECT:LDAP Result Codes}}
 * {{SECT:Glossary}}
 
 Also, the table of contents is now 3 levels deep to ease navigation.
@@ -127,7 +133,7 @@ H3: Performance enhancements
 Too many to list. Some notable changes - ldapadd used to be a couple of orders 
 of magnitude slower than "slapadd -q". It's now at worst only about half the 
 speed of slapadd -q. Some comparisons of all the 2.x OpenLDAP releases are available 
-at {{URL:http://www.highlandsun.com/hyc/scale2007.pdf}}
+at {{URL:http://www.openldap.org/pub/hyc/scale2007.pdf}}
 
 That compared 2.0.27, 2.1.30, 2.2.30, 2.3.33, and HEAD). Toward the latter end 
 of the "Cached Search Performance" chart it gets hard to see the difference 
@@ -145,20 +151,27 @@ processing time is almost invisible; the runtime is limited only by the memory
 bandwidth of the machine. (The search data rate corresponds to about 3.5GB/sec; 
 the memory bandwidth on the machine is only about 4GB/sec due to ECC and register latency.)
 
-No other Directory Server in the world is this fast or this efficient. Couple 
-that with the scalability, manageability, flexibility, and just the sheer 
-know-how behind this software, and nothing else is even remotely comparable.
-
 H3: New overlays
 
+* slapo-constraint (Attribute value constraints)
 * slapo-dds (Dynamic Directory Services, RFC 2589)
 * slapo-memberof (reverse group membership maintenance)
 
 H3: New features in existing Overlays
 
-* slapo-pcache allows cache inspection/maintenance/hot restart
+* slapo-pcache
+  - Inspection/Maintenance 
+    -- the cache database can be directly accessed via
+       LDAP by adding a specific control to each LDAP request; a specific
+       extended operation allows to consistently remove cached entries and entire
+       cached queries
+  - Hot Restart
+    -- cached queries are saved on disk at shutdown, and reloaded if
+      not expired yet at subsequent restart
+
 * slapo-rwm can safely interoperate with other overlays
 * Dyngroup/Dynlist merge, plus security enhancements
+  - added dgIdentity support (draft-haripriya-dynamicgroup)
 
 H3: New features in slapd
 
@@ -170,20 +183,32 @@ H3: New features in libldap
 
 * ldap_sync client API (LDAP Content Sync Operation, RFC 4533)
 
-H3: New clients and tools
+H3: New clients, tools and tool enhancements
 
 * ldapexop for arbitrary extended operations
-* complete support of controls in request/response for all clients
+* Complete support of controls in request/response for all clients
+* LDAP Client tools now honor SRV records 
 
 H3: New build options
 
 * Support for building against GnuTLS
-* Advertisement of LDAP server in DNS
 
 
-H2: Obsolete Features in 2.4
+H2: Obsolete Features Removed From 2.4
+
+These features were strongly deprecated in 2.3 and removed in 2.4.
 
 H3: Slurpd
 
 Please read the {{SECT:Replication}} section as to why this is no longer in
 OpenLDAP
+
+H3: back-ldbm
+
+back-ldbm was both slow and unreliable. Its byzantine indexing code was
+prone to spontaneous corruption, as were the underlying database libraries
+that were commonly used (e.g. GDBM or NDBM). back-bdb and back-hdb are
+superior in every aspect, with simplified indexing to avoid index corruption,
+fine-grained locking for greater concurrency, hierarchical caching for
+greater performance, streamlined on-disk format for greater efficiency
+and portability, and full transaction support for greater reliability.