What is the "query" in Virtual List View control specification?

Question

I am reading Virtual List View control specification

and there is the phrase

contextID values have no validity outside the connection and query with which they were received. A client MUST NOT submit a contextID which it received from a different connection, a different query, or a different server.

I use unboundId library:

public SearchRequest(@NotNull final String baseDN,
                     @NotNull final SearchScope scope,
                     @NotNull final Filter filter,
                     @Nullable final String... attributes)

If I have 2 SearchRequests which are different only in attributes. Will it mean that query are different or not?

Answer 1

The SearchRequests will be different.

I am not clear what you are needing to determine.

As stated it is:

A server-generated contextID MAY be returned to clients. A client receiving a contextID MUST return it unchanged or not return it at all, in a subsequent request which relates to the same list. The purpose of this interaction is to maintain state information between the client and server

Also, unboundid-ldap-sdk is extremely well documented and often with Examples. Set it like:

 ASN1OctetString vlvContextID = null;

And include it with any subsequent request which relates to the same list.

A searchRequest is presented to the LDAP Server and you receive a searchResponse.

A "filter" is is part of the searchRequest and might be like:

"dc=example,dc=com"

Again, there are examples for searchRequest.

LDAP Query is an abstract term that requires an agreed upon connotation.

Most people probably relate LDAP Query to the collection of LDAP Filter parameters and LDAP Operators: (&(objectClass=user)(sn=Smith))

A searchRequest contains 10-11 items which could affect the searchResult even if the Filter is the same.