Re: Encoding for server side sorting and virtual list view

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 11:20 PM 4/11/01 -0400, John Liang wrote:
>If only DER is allowed, then for SortKeyList in Server Side
>Sorting, the tag of "orderingRule [0] MatchingRuleId OPTIONAL"
>should be 0x80 or 0xA0?

They 0x80 and 0xA0 difference indices the kind of data
type being encoded.  0x80 indicates a PRIMITIVE data type
encoding while 0xA0 indicates a CONSTRUCTED data type
encoding.  Both are context specific, zero valued tags.

MatchingRuleId is an OCTET STRING which is a PRIMITIVE
data type while byoffset is a SEQUENCE which is a
CONSTRUCTED data type. 

The following page provide a number of good links to
ASN.1 resources:
  http://www.cs.columbia.edu/~hgs/internet/asn.1.html

Kurt


>Same question for VirtualListViewRequest, the tag of 
> CHOICE {
>        byoffset [0] SEQUENCE {
>          offset       INTEGER (0 .. maxInt)
>          contentCount INTEGER (0 .. maxInt)
>should be 0x80 or 0xA0?
>
>The Netscape Java API uses 0x80 for Server Side Sorting 
>and 0xA0 for Virtual List View? Any reson for the difference?
>
>Thanks,
>--
>John Liang