directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (DIRSNICKERS-58) SearchResultEntry: create digester rules to decode
Date Mon, 31 May 2004 06:12:01 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Sun, 30 May 2004 11:10 PM
       Body:
Here's the ASN.1 for the SearchResultEntry:

        LDAPString ::= OCTET STRING

        AttributeDescription ::= LDAPString

        AttributeValue ::= OCTET STRING

        PartialAttributeList ::= SEQUENCE OF SEQUENCE 
        {
                type    AttributeDescription,
                vals    SET OF AttributeValue 
        }

        SearchResultEntry ::= [APPLICATION 4] SEQUENCE 
        {
                objectName      LDAPDN,
                attributes      PartialAttributeList 
        }


Here's what the tag nesting anatomy of a SearchResultEntry PDU looks like if two attributes,
with 3 values (one with one value and another with two ) are returned for the entry:

16 [0x10000000][80]
        2 [0x02000000][1]
        4 [0x44000000][73]
                 4 [0x04000000][17]
                16 [0x10000000][52]
                        16 [0x10000000][30]
                                 4 [0x04000000][11]
                                17 [0x11000000][15]
                                        4 [0x04000000][8]
                                        4 [0x04000000][3]
                        16 [0x10000000][18]
                                 4 [0x04000000][2]
                                17 [0x11000000][12]
                                        4 [0x04000000][10]
       0 [0x80000000][0]

This is almost the same as the AddRequest footprint here:


16 [0x10000000][80]
        2 [0x02000000][1]
        8 [0x48000000][73]
                 4 [0x04000000][17]
                16 [0x10000000][52]
                        16 [0x10000000][30]
                                 4 [0x04000000][11]
                                17 [0x11000000][15]
                                        4 [0x04000000][3]
                                        4 [0x04000000][8]
                        16 [0x10000000][18]
                                 4 [0x04000000][2]
                                17 [0x11000000][12]
                                        4 [0x04000000][10]
        0 [0x80000000][0]

The only difference is the 8 [0x48000000] for AddRequest and 4 [0x44000000] for SearchResultEntry.


---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/DIRSNICKERS-58?page=comments#action_35832

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSNICKERS-58

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-58
    Summary: SearchResultEntry: create digester rules to decode
       Type: Task

     Status: In Progress
   Priority: Major

    Project: Directory Snickers
 Components: 
             LDAP Provider

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Fri, 28 May 2004 11:14 PM
    Updated: Sun, 30 May 2004 11:10 PM
    Due:     Tue, 1 Jun 2004 12:00 AM

Description:
 The digester rules to create and build a SearchResultEntry need to be created and test cases
for decoding should pass.  This is probably sencond hardest.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message