Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Sun, 29 Mar 2015 13:04:54 +0000 (UTC)
From: "Kai Zheng (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12786525.1427634273000.62330.1427634294340@Atlassian.JIRA>
In-Reply-To: <JIRA.12786525.1427634273000@Atlassian.JIRA>
References: <JIRA.12786525.1427634273000@Atlassian.JIRA>
 <JIRA.12786525.1427634273690@arcas>
Subject: [jira] [Created] (DIRKRB-199) [KrbClient] Support both blocking and
 event based network transport
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kai Zheng created DIRKRB-199:
--------------------------------

             Summary: [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)