[Date Prev][Date Next] [Chronological] [Thread] [Top]

A question about the sssvlv overlay



Hi all,

When using the sssvlv overlay I see the following behaviour:
(a) Updating an attribute value while an sssvlv request is active:
    1. do a request containing a vlv control and a sort control, which returns a subset of a total result set defined by the search parameters, and the context id for the request.    2. update an attribute value in one of the objects which was returned in the result set    3. repeat the request in step 1, specifying the context id in the vlv control, which returns the same results as in step 1, except that the attribute value updated in step 2 has changed
(b) Deleting an object while an sssvlv request is active:
    1. do a request containing a vlv control and a sort control, which returns a subset of a total result set defined by the search parameters, and the context id for the request.    2. delete one of the objects which was returned in the result set    3. repeat the request in step 1, specifying the context id in the vlv control, which returns the same results as in step 1, except that the object deleted in step 2 has gone
(c) Adding an object while an sssvlv request is active:
    1. do a request containing a vlv control and a sort control, which returns a subset of a total result set defined by the search parameters, and the context id for the request.    2. add a new object which would have been returned by step 1 if the object had existed already    3. repeat the request in step 1, specifying the context id in the vlv control, which returns the same results as in step 1. The new object is not returned in the results.
(d) Deleting and re-adding an object while an sssvlv request is active:
    1. do a request containing a vlv control and a sort control, which returns a subset of a total result set defined by the search parameters, and the context id for the request.    2. delete one of the objects which was returned in the result set    3. repeat the request in step 1, specifying the context id in the vlv control, which returns the same results as in step 1, except that the object deleted in step 2 has gone    4. add the deleted object back in    5. repeat the request in step 1, specifying the context id in the vlv control, which returns the same results as in step 1. The object deleted in step 2 is back.
Is this the expected behaviour of the sssvlv overlay?
Or is the behaviour in (c) a bug?
The draft RFC http://tools.ietf.org/html/draft-ietf-ldapext-ldapv3-vlv-09 does not specify what the behaviour ought to be as far as I can see, but the current behaviour seems inconsistent.
[tested using openldap 2.4.26 patched with all the available fixes to the sssvlv overlay]
Chris