You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/05/31 04:13:01 UTC

[jira] Commented: (DIRSNICKERS-60) SearchResultReference: create digester rules to decode

The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Sun, 30 May 2004 7:12 PM
       Body:
Here's the ASN.1 for a SearchResultReference:

LDAPString ::= OCTET STRING
LDAPURL ::= LDAPString -- limited to characters permitted in URLs
SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL

Here's the tag nesting anatomy for SearchResultReference with 2 urls and no controls:

16 [0x10000000][122]
         2 [0x02000000][1]
        19 [0x53000000][115]
                4 [0x04000000][63]
                4 [0x04000000][48]
         0 [0x80000000][0]

Looks like we have 2 rule registrations total.  One to create the SearchResultReference and another to create and add urls to it.

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-60
    Summary: SearchResultReference: 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:19 PM
    Updated: Sun, 30 May 2004 7:12 PM
    Due:     Wed, 2 Jun 2004 12:00 AM

Description:
The digester rules to create and build a SearchRequest need to be created and test cases for decoding should pass.


---------------------------------------------------------------------
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