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/03/29 16:22:52 UTC
[jira] [Commented] (DIRKRB-199) [KrbClient] Support both blocking
and event based network transport
[ https://issues.apache.org/jira/browse/DIRKRB-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385786#comment-14385786 ]
Kai Zheng commented on DIRKRB-199:
----------------------------------
commit ff0200f8bb71a9e265e1339589aa773508371f21
Author: Drankye <dr...@gmail.com>
Date: Sun Mar 29 22:19:14 2015 +0800
DIRKRB-199. Support both blocking and event based network transport
> [KrbClient] Support both blocking and event based network transport
> -------------------------------------------------------------------
>
> Key: DIRKRB-199
> URL: https://issues.apache.org/jira/browse/DIRKRB-199
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
>
> This is to enhance KrbClient to:
> 1. Separate concrete implementation logic from it, having it focus on API level;
> 2. Separate network transport aspect from KrbClient implementation and make transport part can be swapped in and out;
> 3. Have the event based model for the long term targeting concurrent requests processing scenarios;
> 4. By default it uses blocking mode transport, for most simple cases, with much less overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)