[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LCUP and PSearch on Sync-And-Persist
Timothy Hahn wrote:
What about a client that wants to "hold off" on handling search requests
until it knows that its
information is "close" to what is held in the server? "close" being
defined as the "synchronization"
part being done and only "updates" will be sent from here forward.
I think this may be a valid requirement for LCUP. With Persistent
Search, a client can tell where the stream of changes begins, but only
after the first change is received (by looking for the presence of an
entryChangeControl in the SearchResultEntry PDU).