Re: [ldapext] VLV: a particular target entry

["David Boreham" <david_list@boreham.org>]

Discussion point: what if the complete list were to change between
two VLV requests from a client ? How does a cookie help us to
render something unconfusing to the client ?

If, as I hope, it's clear that this is a hopeless exercise, then
let's think about a continuum of progressively less and less
major change to the list between consecutive requests...

Where on this continuum would we decide that there was
sufficiently little change to make it possible to use cookies
or whatever other protocol devices to ensure that the user
isn't 'confused' by the list change ?


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext