From: Gavin Henry Date: Fri, 6 Mar 2009 17:50:16 +0000 (+0000) Subject: First attempt to visualise refreshOnly and refreshAndPersist modes of LDAP Sync Protocol. X-Git-Tag: ACLCHECK_0~731 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=86afc76f8e2067cfb30fec78b3af3d2b0d1eb8dc;p=openldap First attempt to visualise refreshOnly and refreshAndPersist modes of LDAP Sync Protocol. --- diff --git a/doc/guide/admin/Makefile b/doc/guide/admin/Makefile index 1a8205fc4c..2af9590c6d 100644 --- a/doc/guide/admin/Makefile +++ b/doc/guide/admin/Makefile @@ -63,9 +63,13 @@ sdf-img: \ config_local.png \ config_ref.png \ config_repl.png \ + delta-syncrepl.png \ dual_dc.png \ intro_dctree.png \ intro_tree.png \ + ldap-sync-refreshandpersist.png \ + ldap-sync-refreshonly.png \ + n-way-multi-master.png \ push-based-complete.png \ push-based-standalone.png \ refint.png \ diff --git a/doc/guide/admin/ldap-sync-refreshandpersist.png b/doc/guide/admin/ldap-sync-refreshandpersist.png new file mode 100644 index 0000000000..f6a2232ce8 Binary files /dev/null and b/doc/guide/admin/ldap-sync-refreshandpersist.png differ diff --git a/doc/guide/admin/ldap-sync-refreshonly.png b/doc/guide/admin/ldap-sync-refreshonly.png new file mode 100644 index 0000000000..7f4a95e740 Binary files /dev/null and b/doc/guide/admin/ldap-sync-refreshonly.png differ diff --git a/doc/guide/images/src/ldap-sync-refreshandpersist.svg b/doc/guide/images/src/ldap-sync-refreshandpersist.svg new file mode 100644 index 0000000000..d5047ff20b --- /dev/null +++ b/doc/guide/images/src/ldap-sync-refreshandpersist.svg @@ -0,0 +1,4853 @@ + + + + + + + Firewall2 + + + + wall + brick + computer + networksym + + + + + Open Clip Art Library + + + + + HASH(0x89c79d4) + + + + + HASH(0x89c79d4) + + + + image/svg+xml + + + en + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LDAP Content Synchronization Operation - refreshAndPersist + + + + + 1. Same as refreshOnly request,but refreshAndPersist modeset. + Server + Client + 2a. Same as refreshOnly mode. + 2b. This time, send a Sync InfoMessage to client indicating refreshstage is done and then enters the persist stage + 3. After receiving the message, the client will construct a synchronized copy as describedin the refreshOnly mode. + 4. Server can now send change notifications based on original SyncSearch Request + 6. Server may terminate Sync Operation.If it doesn't provide a cookie, a fullrefresh is needed by client. + 5a. For returned entries the SearchResultEntry will have the Sync State Control set to either;add, delete or modify + + + + 5b. Waits for server to send entries + 7. Client refreshes if disconnects and provides last syncCookie if ithas one. + + diff --git a/doc/guide/images/src/ldap-sync-refreshonly.svg b/doc/guide/images/src/ldap-sync-refreshonly.svg new file mode 100644 index 0000000000..27f6f4032d --- /dev/null +++ b/doc/guide/images/src/ldap-sync-refreshonly.svg @@ -0,0 +1,4814 @@ + + + + + + + Firewall2 + + + + wall + brick + computer + networksym + + + + + Open Clip Art Library + + + + + HASH(0x89c79d4) + + + + + HASH(0x89c79d4) + + + + image/svg+xml + + + en + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LDAP Content Synchronization Operation - refreshOnly + + + + + + + 1. Initial client copy Syncrequest - search requestwith Sync Request Controlwith mode set to 'resfreshOnly' + Server + Client + 2a. Returns content matching search and with each entry provides a SyncState Control which contains the 'entryUUID' + 2b. Follows with a SearchResultDone with a 'Sync Done Control' whichprovides the syncCookie - this cookierepresents the session state. + 3. Polls for updates providing the previously issued syncCookie + 4a. Use present or delete phase?Both can be used, present brings client copy up to a point where deletecan begin. + 4b. Server uses syncCookie as an indicator of what client got before andthen sends copies of entries that havechanged. All attributes are sent. + 5. Repeat using syncCookie, i.e.go back to step 3. + + +