RE: Fix for VLV draft.

["John Liang" <John.Liang@openwave.com>]

> -----Original Message-----
> From: Jim Sermersheim [mailto:jimse@novell.com]
> Sent: Tuesday, January 30, 2001 1:34 PM
> To: ietf-ldapext@netscape.com; John.Liang@openwave.com
> Subject: RE: Fix for VLV draft.
> 
> 
> >>> "John Liang" <John.Liang@openwave.com> 1/29/01 10:35:29 AM >>>
> >I want to ask a few questions about this topic:
> >
> >1> if the control is not critical, and there is an error in server side
> >sorting control
> >or virutal list view control, the server is supposed to send back all
> >unsorted result.
> 
> No, during processing, if there is an error (due to the control 
> being processed or otherwise), processing stops, and the 
> searchResultDone is returned with (some) error code.
> 
> >if the server returns all unsorted entries successfully,
> >is LDAP searchResultDone message supposed to return LDAP_SUCCESS or
> >other(80)?
> >Must we include sssResponse and vlvResponse with corresponding 
> error code?
> 
> If the server returns all unsorted entries successfully, it is 
> because the server does not support the vlv and sss controls, and 
> they are not marked critical. Thus they are ignored and the 
> search is processed as if it never had the controls. There is no 
> sss or vlv response code in this case because the server doesn't 
> recognise them.
 
Jim,

It sounds different from RFC2891(LDAP Control Extension for Server
Side Sorting of Search Results), chapter 2, item 4:

4 - If the server supports this sorting control but for some reason
       cannot sort the search results using the specified sort keys and
       the client specified FALSE for the control's criticality field,
       then the server should return all search results unsorted and
       include the sortKeyResponseControl in the searchResultDone
       message.

It shows that if the server supportes this control, the unsorted result
could be sent back under certain conditions.

Any comments?

Thanks,
--
John Liang