directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSHARED-92) See if we can make the protocol codec pluggable as well.
Date Sat, 19 Feb 2011 05:03:38 GMT

    [ https://issues.apache.org/jira/browse/DIRSHARED-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996700#comment-12996700
] 

Alex Karasulu commented on DIRSHARED-92:
----------------------------------------

Once we can determine whether or not we can use the same protocol codec factory for both the
server and the client we know just how to make this piece pluggable. 

We will need to separate this out into it's own ldap-protocol-codec module. It will not be
an API. The server and studio will access this component's interface which is a MINA interface
(ProtocolCodecFactory) via the LdapCodecService. 

> See if we can make the protocol codec pluggable as well.
> --------------------------------------------------------
>
>                 Key: DIRSHARED-92
>                 URL: https://issues.apache.org/jira/browse/DIRSHARED-92
>             Project: Directory Shared
>          Issue Type: Sub-task
>    Affects Versions: 1.0-M1
>         Environment: All
>            Reporter: Alex Karasulu
>             Fix For: 1.0-M2
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The codec can offer different protocol codec factories since it is a factory of protocol
codecs. This might allow us to leverage other network libraries like Grizzly, and Netty 3.0
in addition to Apache MINA, which helps compare differences. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message