You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kai Zheng (JIRA)" <ji...@apache.org> on 2015/04/12 14:44:12 UTC
[jira] [Updated] (DIRKRB-200) [KDC] Pluggable KDC server
implementation based on different network transport model
[ https://issues.apache.org/jira/browse/DIRKRB-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kai Zheng updated DIRKRB-200:
-----------------------------
Summary: [KDC] Pluggable KDC server implementation based on different network transport model (was: [KDC] Pluggable network transport for KDC server)
> [KDC] Pluggable KDC server implementation based on different network transport model
> ------------------------------------------------------------------------------------
>
> Key: DIRKRB-200
> URL: https://issues.apache.org/jira/browse/DIRKRB-200
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
>
> This is to enhance KDC server to:
> * Separate *KdcServer* implementation from the API;
> * Make KdcServer implementation can be swapped in and out;
> * Allow to support and plugin network transport part;
> * By default using per-connection thread model for simple usage or test;
> * Have event based request processing model for large cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)