Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D12C7200D03 for ; Sat, 9 Sep 2017 17:47:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CFCFB160BE1; Sat, 9 Sep 2017 15:47:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1FF001609B9 for ; Sat, 9 Sep 2017 17:47:06 +0200 (CEST) Received: (qmail 82589 invoked by uid 500); 9 Sep 2017 15:47:05 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 82579 invoked by uid 99); 9 Sep 2017 15:47:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Sep 2017 15:47:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 760C01A5B4B for ; Sat, 9 Sep 2017 15:47:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zVm50R9HPzRe for ; Sat, 9 Sep 2017 15:47:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4F8065FDD8 for ; Sat, 9 Sep 2017 15:47:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 65D37E00C7 for ; Sat, 9 Sep 2017 15:47:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id EA19324143 for ; Sat, 9 Sep 2017 15:47:00 +0000 (UTC) Date: Sat, 9 Sep 2017 15:47:00 +0000 (UTC) From: "Stefan Seelmann (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DIRAPI-179) Referral Hop Count MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 09 Sep 2017 15:47:08 -0000 [ https://issues.apache.org/jira/browse/DIRAPI-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRAPI-179: ----------------------------------- Fix Version/s: 2.0.0 > Referral Hop Count > ------------------ > > Key: DIRAPI-179 > URL: https://issues.apache.org/jira/browse/DIRAPI-179 > Project: Directory Client API > Issue Type: Improvement > Affects Versions: 1.0.0-M20 > Reporter: Robert Hou > Fix For: 1.0.0-RC3, 2.0.0 > > > As we found, there is already one related issue DIRAPI-61 for Referral Chase. Then we want API to support Hop Count when chase referral.That means API can let user control the hop count when API chase referral. Netscape LDAP SDK already has this featue, we can refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)