[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Réf. : Re: ACLs Enhancements (ITS#3515)
This is a multipart message in MIME format.
--=_alternative 005F2274C1256F94_=
Content-Type: text/plain; charset="us-ascii"
OK
1) I send you a PDF version jean-etienne-schwartz-050125-dynacl.pdf
2) Yes, I resubmit it with the good name
3) For me dynamic means that ACL come with the current node, automatically
(see pdf)
a) the keyword we use is 'dynacl'
b) and d) no interactions with ACI or SET
Pierangelo Masarati <openldap-its@OpenLDAP.org>
25/01/05 18:00
Pour : jean-etienne.schwartz@bull.net
cc :
Objet : Re: ACLs Enhancements (ITS#3515)
A few very preliminary comments, while I'm reading the details of your
submission:
1) a .pdf version of the doc is mandatory; with OpenOffice your document
looks
terrible because of the font choice.
2) I cannot access the example configuration file; bad URL?
3) I note that ACLs in HEAD have been modified quite a bit with respect to
RE22
code; significantly:
a) another implementation with the name dynamic ACLs is present, where
dynamic means "run-time loadable"
b) ACIs now use this API
c) "disclose" and "manage" access levels have been added, with the
former
being implemented (it's already complete in back-sql and portions are
implemented in back-bdb/hdb/ldbm).
d) sets have been partially reworked
Although the above may not directly impact/conflict with your submission,
I
think a lot of workload may be required to integrate it with HEAD code,
but this
is the only way to go if you want it to be considered, because RE22 is
feature
frozen and 2.3 (essentially, HEAD) is being rolled out.
Further comments will follow; by now, thanks for the contribution.
p.
--=_alternative 005F2274C1256F94_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">OK</font>
<br><font size=2 face="sans-serif">1) I send you a PDF version jean-etienne-schwartz-050125-dynacl.pdf</font>
<br><font size=2 face="sans-serif">2) Yes, I resubmit it with the good name</font>
<br><font size=2 face="sans-serif">3) For me dynamic means that ACL come with the current node, automatically (see pdf)</font>
<br><font size=2 face="sans-serif"> a) the keyword we use is 'dynacl'</font>
<br><font size=2 face="sans-serif"> b) and d) no interactions with ACI or SET</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Pierangelo Masarati <openldap-its@OpenLDAP.org></b></font>
<p><font size=1 face="sans-serif">25/01/05 18:00</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> Pour : jean-etienne.schwartz@bull.net</font>
<br><font size=1 face="sans-serif"> cc : </font>
<br><font size=1 face="sans-serif"> Objet : Re: ACLs Enhancements (ITS#3515)</font></table>
<br>
<br><font size=2 face="Courier New">A few very preliminary comments, while I'm reading the details of your<br>
submission:<br>
<br>
1) a .pdf version of the doc is mandatory; with OpenOffice your document looks<br>
terrible because of the font choice.<br>
2) I cannot access the example configuration file; bad URL?<br>
3) I note that ACLs in HEAD have been modified quite a bit with respect to RE22<br>
code; significantly:<br>
a) another implementation with the name dynamic ACLs is present, where<br>
dynamic means "run-time loadable"<br>
b) ACIs now use this API<br>
c) "disclose" and "manage" access levels have been added, with the former<br>
being implemented (it's already complete in back-sql and portions are<br>
implemented in back-bdb/hdb/ldbm).<br>
d) sets have been partially reworked<br>
Although the above may not directly impact/conflict with your submission, I<br>
think a lot of workload may be required to integrate it with HEAD code, but this<br>
is the only way to go if you want it to be considered, because RE22 is feature<br>
frozen and 2.3 (essentially, HEAD) is being rolled out.<br>
<br>
Further comments will follow; by now, thanks for the contribution.<br>
<br>
p.<br>
<br>
</font>
<br>
<br>
--=_alternative 005F2274C1256F94_=--