Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 68898 invoked from network); 13 Dec 2007 05:18:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Dec 2007 05:18:50 -0000 Received: (qmail 65812 invoked by uid 500); 13 Dec 2007 05:18:37 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 65784 invoked by uid 500); 13 Dec 2007 05:18:37 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 65775 invoked by uid 99); 13 Dec 2007 05:18:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2007 21:18:37 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xu.regis@gmail.com designates 209.85.146.182 as permitted sender) Received: from [209.85.146.182] (HELO wa-out-1112.google.com) (209.85.146.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2007 05:18:15 +0000 Received: by wa-out-1112.google.com with SMTP id k22so903554waf.18 for ; Wed, 12 Dec 2007 21:18:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=TBj3aFb+dlFU2Ri5WxQxMGqevMDHZHFnmomTs9lOLLY=; b=puvCS34cWhCAJwsLqBsX/lqIEPrjV6eaS1SHpi45+YZoO/X3eroXZ/TIISzuZun6AwU5SYPpA9fVawyvuOEfqSShzLxWxGCvtDgkKqVTwJ0QJJvAbhU6rOgoYDBQqyu9uSCrMc0kKyqqeK9YNKSz4ZC2Iwt0hdlw+RmlbhIShdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=W7dYBLlzyasjh23uLOPOP+4i/bvvWex6iiMpreWfVf2/ohJ6v2zK6Ap5JREJuwAcxin1/krGm/vPRIpCY4XdxpGcU/NxI9F8939YPg5atUmI7H9flO2VIDL2X2QEFzxqx9JSELXSHzamPhvIQiSyk43PuZS1gpI2xR9/pRpfT2k= Received: by 10.115.76.1 with SMTP id d1mr1762564wal.108.1197523098921; Wed, 12 Dec 2007 21:18:18 -0800 (PST) Received: from ?9.181.107.81? ( [220.248.0.145]) by mx.google.com with ESMTPS id v32sm9594131wah.2007.12.12.21.18.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 12 Dec 2007 21:18:17 -0800 (PST) Message-ID: <4760C09A.3030002@gmail.com> Date: Thu, 13 Dec 2007 13:18:18 +0800 From: Regis User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: dev@harmony.apache.org Subject: Re: [classlib][jndi][compat] Shoud Harmony support ri's ldap provider specific properties? References: <475E1F1F.3000001@gmail.com> <6e47b64f0712122030m3cf102f9na3c569f440e2f2f7@mail.gmail.com> In-Reply-To: <6e47b64f0712122030m3cf102f9na3c569f440e2f2f7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Sure, we can implement these features without looking to the code, but the question is should we use the same property name as ri ? such as com.sun.jndi.ldap.connect.timeout, i prefer to replace it by org.apache.harmony.jndi.ldap.connect.timeout. Best Regards, Regis. Stepan Mishura wrote: > On 12/11/07, Regis wrote: >> Hi, >> >> There are some provider-specific environment properties defined in ri's >> ldap provider, such as, >> com.sun.jndi.ldap.connect.timeout, com.sun.jndi.ldap.trace.ber >> >> I'm not sure how to deal with these properties, should we support them >> for compatibility reason > > Are this properties well documented/included to the spec? IOW, is it > possible to implement them without looking to the code? > > Thanks, > Stepan. > >> or we just supply Harmony's provider specific properties, like >> org.apache.harmony.jndi.ldap.timeout? >> >> Any thoughts or suggestions? >> >> Best Regards, >> Regis. >> >