Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <55A4EF28.2080002@evolveum.com>
Date: Tue, 14 Jul 2015 13:14:48 +0200
From: Radovan Semancik <radovan.semancik@evolveum.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: dev@directory.apache.org
Subject: Re: 389 Directory Server support in API
References: <55A4CD24.3080600@evolveum.com> <55A4D8A6.7060002@gmail.com>
 <55A4DEC3.2030600@evolveum.com>
 <CADPkm87-Rtq2KBGMZsvnxQmLXN9SDhpsNoNC_JAcvvh_sBaBoQ@mail.gmail.com>
 <etPan.55a4eac0.3c98d0d5.327@lpm.local>
In-Reply-To: <etPan.55a4eac0.3c98d0d5.327@lpm.local>
Content-Type: multipart/alternative;
 boundary="------------070200030001040409030207"

This is a multi-part message in MIME format.
--------------070200030001040409030207
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 07/14/2015 12:56 PM, Ludovic Poitou wrote:
> The general rule around standard support is =E2=80=9Cbe flexible in wha=
t you=20
> accept, strict about what you produce=E2=80=9D.
> This should apply to the LDAP APIs as well.

This is not necessarily the best option:=20
https://github.com/martinthomson/postel-was-wrong/blob/master/draft-thoms=
on-postel-was-wrong.md

I think that there needs to be some balance between strictness and=20
tolerance. However, Apache Directory API is not widespread enough. So=20
even if it is strict it is unlikely that it will create enough pressure=20
on outdated LDAP servers. And if it will work only with ApacheDS and=20
OpenLDAP then it will never become widespread. So I would be inclined=20
towards more tolerance in the API to make it practical.

--=20
Radovan Semancik
Software Architect
evolveum.com


--------------070200030001040409030207
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">On 07/14/2015 12:56 PM, Ludovic Poitou
      wrote:<br>
    </div>
    <blockquote cite=3D"mid:etPan.55a4eac0.3c98d0d5.327@lpm.local"
      type=3D"cite">
      <style>body{font-family:Helvetica,Arial;font-size:13px}</style>
      <div id=3D"bloop_customfont"
        style=3D"font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">The general
        rule around standard support is =E2=80=9Cbe flexible in what you =
accept,
        strict about what you produce=E2=80=9D.</div>
      <div id=3D"bloop_customfont"
        style=3D"font-family:Helvetica,Arial;font-size:13px; color:
        rgba(0,0,0,1.0); margin: 0px; line-height: auto;">This should
        apply to the LDAP APIs as well.</div>
    </blockquote>
    <br>
    This is not necessarily the best option:
<a class=3D"moz-txt-link-freetext" href=3D"https://github.com/martinthoms=
on/postel-was-wrong/blob/master/draft-thomson-postel-was-wrong.md">https:=
//github.com/martinthomson/postel-was-wrong/blob/master/draft-thomson-pos=
tel-was-wrong.md</a><br>
    <br>
    I think that there needs to be some balance between strictness and
    tolerance. However, Apache Directory API is not widespread enough.
    So even if it is strict it is unlikely that it will create enough
    pressure on outdated LDAP servers. And if it will work only with
    ApacheDS and OpenLDAP then it will never become widespread. So I
    would be inclined towards more tolerance in the API to make it
    practical.<br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Radovan Semancik
Software Architect
evolveum.com
</pre>
  </body>
</html>

--------------070200030001040409030207--