You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by di...@incubator.apache.org on 2004/09/25 21:20:33 UTC

[jira] Commented: (DIRLDAP-6) need to reasses this provider based arch to common message framework

The following comment has been added to this issue:

     Author: Alex Karasulu
    Created: Sat, 25 Sep 2004 12:20 PM
       Body:
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:
  http://issues.apache.org/jira/browse/DIRLDAP-6?page=comments#action_53409

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRLDAP-6

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
 Components: 
             Common

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

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

Description:
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?




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