On 1/20/2016 6:06 PM, Fraser Tweedale wrote:
On Wed, Jan 20, 2016 at 12:44:38PM -0600, Endi Sukma Dewata wrote:
On 1/19/2016 8:07 PM, Fraser Tweedale wrote:
Rebase was needed for the remaining patches; 0060-2 and 0061-2 attached.
Thanks, Fraser
ACK for both of them.
Thanks! Pushed to master
- 41717cb774f53e30caf7a57c2e07526445bf0988 Ensure config store commits refresh file-based profile data - 0af4a9393ce38216689e9afe17514b9441784133 Handle LDAPProfileSubsystem delete-then-recreate races
Just wondering, would it be possible to distinguish local and remote persistent search results? So if a profile is changed on a machine, the profile object will be updated immediately in memory, then persistent search result for that modification will be ignored since it's initiated locally. Other machines, however, will pick up the changes from the persistent search result since it's initiated remotely.
This is indeed accomplished by the tracking of the entryUSN resulting from a change (via the PostReadControl) and the deleted entries.
Right. I was just thinking suppose the persistent search result contains a 'modifiedBy' attribute that stores the hostname, we might be able use that to ignore local changes without storing anything in the memory. -- Endi S. Dewata