directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (DIRLDAP-6) need to reasses this provider based arch to common message framework
Date Sat, 25 Sep 2004 19:20:33 GMT
The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Sat, 25 Sep 2004 12:20 PM
Several of these questions have already been answered by slow migrational changes that have
been made to account for stateful decoder/encoder usage.  

I think the majority of changes have been made to introduce asynch processing by codecs. 
We only need to cleanup and make this SPI thing look a bit more professional.  Right now there
is a DecoderSpi and EncoderSpi class.  This looks strange so we need need some cosmetic changes
here.  This can be don any time.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: DIRLDAP-6
    Summary: need to reasses this provider based arch to common message framework
       Type: Task

     Status: In Progress
   Priority: Major

    Project: Directory LDAP

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Tue, 16 Mar 2004 8:40 PM
    Updated: Sat, 25 Sep 2004 12:20 PM

Need to reassess the provider based architecture to the common message framework around LDAP
ASN.1 Messsage types.  Here are the 
key points:

1). Do we continue to use a provider architecture?
2). Should we change the interfaces to make it easier to work with NIO constructs.
3). How does it work with the stateful decoders and encoders?

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message