directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enrique Rodriguez <erodrig...@apache.org>
Subject Re: [SPAM] svn commit: r168500 - /directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml /directory/sitedocs/trunk/xdocs/subprojects/providers.xml
Date Fri, 06 May 2005 21:22:12 GMT
Alex,

Regarding this commit, I'm curious what "correcting some language" 
refers to.  Unfortunately, it's really hard to tell with the commit 
combining corrections and formatting changes.  I made an educated guess 
at some of the RFC's and features covered regarding the LDAP protocol, 
so I was wondering if that's what you updated.

I apologize for the tab-formatting and DOS line-endings.  I am using an 
XML plug-in in Eclipse and hadn't realized how much munging it was doing.

-enrique


akarasulu@apache.org wrote:
> Author: akarasulu
> Date: Thu May  5 19:34:25 2005
> New Revision: 168500
> 
> URL: http://svn.apache.org/viewcvs?rev=168500&view=rev
> Log:
> changes ...
> 
>  o fixing tab based formating
>  o changing links to use providers subproject directory that contains all
>  o correcting some language
> 
> 
> Added:
>     directory/sitedocs/trunk/xdocs/subprojects/providers.xml
>       - copied, changed from r168482, directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml
> Removed:
>     directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml
> 
> Copied: directory/sitedocs/trunk/xdocs/subprojects/providers.xml (from r168482, directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml)
> URL: http://svn.apache.org/viewcvs/directory/sitedocs/trunk/xdocs/subprojects/providers.xml?p2=directory/sitedocs/trunk/xdocs/subprojects/providers.xml&p1=directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml&r1=168482&r2=168500&rev=168500&view=diff
> ==============================================================================
> --- directory/sitedocs/trunk/xdocs/subprojects/protocol-providers.xml (original)
> +++ directory/sitedocs/trunk/xdocs/subprojects/providers.xml Thu May  5 19:34:25 2005
> @@ -1,101 +1,101 @@
>  <?xml version="1.0" encoding="UTF-8"?>
>  <document>
> -	<properties>
> -		<author email="erodriguez@apache.org">Enrique Rodriguez</author>
> -		<title>Protocol Provider Subprojects</title>
> -	</properties>
> -	<body>
> -		<section name="Protocol Providers">
> -			<p> The Apache Directory Project's Protocol Providers are Java implementations
of 
> -				standard Internet services. These Protocol Providers, in conjunction with the MINA

> -				network layer and the Apache Directory read-optimized backing store, provide 
> -				easy-to-use yet fully-featured Internet services. As implemented within the Apache

> -				Directory, these services benefit from: </p>
> -			<ul>
> -				<li>Standard directory model and schema support</li>
> -				<li>Standard LDAP data interchange format (LDIF) (RFC 2849)</li>
> -				<li>JMX remote management (JSR 160, JSR 28)</li>
> -				<li>Optional LDAP management</li>
> -				<li>UDP and TCP Support (MINA)</li>
> -				<li>Traffic throttling (MINA)</li>
> -				<li>Overload shielding (MINA)</li>
> -				<li>Easy POJO embeddability for containers such as Geronimo, JBoss, and OSGi</li>
> -			</ul>
> -			<table>
> -				<tr>
> -					<th>Name</th>
> -					<th>Description</th>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="ldap/index.html">Lightweight Directory Access Protocol (LDAP) 
> -							Provider</a>
> -					</td>
> -					<td>
> -						<p> An LDAP implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc2251.html">RFC 2251</a>. Apache LDAP

> -							provides lightweight access to the Apache Directory backing store.</p>
> -					</td>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="kerberos/index.html">Kerberos Protocol Provider</a>
> -					</td>
> -					<td>
> -						<p> A Kerberos implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc1510.html">RFC 1510</a>. Apache 
> -							Kerberos verifies the identities of principals (users or services) on 
> -							an unprotected network using principal information stored in the Apache 
> -							Directory backing store.</p>
> -					</td>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="changepw/index.html">Change Password Protocol Provider</a>
> -					</td>
> -					<td>
> -						<p> A Change Password implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc3244.html">RFC 3244</a>. Apache 
> -							Change Password uses Kerberos infrastructure to allow users to securely 
> -							set initial passwords or to change existing passwords stored in the 
> -							Apache Directory backing store.</p>
> -					</td>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="dns/index.html">Domain Name System (DNS) Protocol Provider</a>
> -					</td>
> -					<td>
> -						<p> A DNS implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc1034.html">RFC 1034</a>. Apache DNS

> -							serves host name to address mappings and other resource record types 
> -							using resource records stored in the Apache Directory backing store.</p>
> -					</td>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="ntp/index.html">Network Time Protocol (NTP) Provider</a>
> -					</td>
> -					<td>
> -						<p> An NTP implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc2030.html">RFC 2030</a>. Apache NTP

> -							supports time synchronization for LDAP replication and the Kerberos 
> -							protocol, eliminating the need for external infrastructure.</p>
> -					</td>
> -				</tr>
> -				<tr>
> -					<td>
> -						<a href="dhcp/index.html">Dynamic Host Configuration Protocol (DHCP) 
> -							Provider</a>
> -					</td>
> -					<td>
> -						<p> A DHCP implementation based on <a 
> -							href="http://www.faqs.org/rfcs/rfc2131.html">RFC 2131</a>. Apache DHCP

> -							helps configure hosts using configuration information stored in the 
> -							Apache Directory backing store.</p>
> -					</td>
> -				</tr>
> -			</table>
> -		</section>
> -	</body>
> +  <properties>
> +      <author email="akarasulu@apache.org">Alex Karasulu</author>
> +      <author email="erodriguez@apache.org">Enrique Rodriguez</author>
> +    <title>Protocol Provider Subprojects</title>
> +  </properties>
> +  <body>
> +    <section name="Protocol Providers">
> +      <p> The Apache Directory Project's Protocol Providers are Java implementations
of
> +        standard Internet services. These Protocol Providers, in conjunction with the
MINA
> +        network layer and the Apache Directory read-optimized backing store, provide
> +        easy-to-use yet fully-featured Internet services. As implemented within the
Apache
> +        Directory, these services benefit from: </p>
> +      <ul>
> +        <li>Standard directory model and schema support</li>
> +        <li>Standard LDAP data interchange format (LDIF) (RFC 2849)</li>
> +        <li>Optional LDAP management</li>
> +        <li>UDP and TCP Support (MINA)</li>
> +        <li>Traffic throttling (MINA)</li>
> +        <li>Overload shielding (MINA)</li>
> +        <li>Easy POJO embeddability for containers such as Geronimo, JBoss, and
OSGi</li>
> +      </ul>
> +      <table>
> +        <tr>
> +          <th>Name</th>
> +          <th>Description</th>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/ldap/index.html">Lightweight Directory Access Protocol
(LDAP)
> +              Provider</a>
> +          </td>
> +          <td>
> +            <p> An LDAP implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc2251.html">RFC 2251</a>. Apache
LDAP
> +              provides lightweight access to the Apache Directory backing store.</p>
> +          </td>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/kerberos/index.html">Kerberos Protocol Provider</a>
> +          </td>
> +          <td>
> +            <p> A Kerberos implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc1510.html">RFC 1510</a>. Apache
> +              Kerberos verifies the identities of principals (users or services) on
> +              an unprotected network using principal information stored in the Apache
> +              Directory backing store.</p>
> +          </td>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/changepw/index.html">Change Password Protocol Provider</a>
> +          </td>
> +          <td>
> +            <p> A Change Password implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc3244.html">RFC 3244</a>. Apache
> +              Change Password uses Kerberos infrastructure to allow users to securely
> +              set initial passwords or to change existing passwords stored in the
> +              Apache Directory backing store.</p>
> +          </td>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/dns/index.html">Domain Name System (DNS) Protocol
Provider</a>
> +          </td>
> +          <td>
> +            <p> A DNS implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc1034.html">RFC 1034</a>. Apache
DNS
> +              serves host name to address mappings and other resource record types
> +              using resource records stored in the Apache Directory backing store.</p>
> +          </td>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/ntp/index.html">Network Time Protocol (NTP) Provider</a>
> +          </td>
> +          <td>
> +            <p> An NTP implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc2030.html">RFC 2030</a>. Apache
NTP
> +              supports time synchronization for LDAP replication and the Kerberos
> +              protocol, eliminating the need for external infrastructure.</p>
> +          </td>
> +        </tr>
> +        <tr>
> +          <td>
> +            <a href="providers/dhcp/index.html">Dynamic Host Configuration Protocol
(DHCP)
> +              Provider</a>
> +          </td>
> +          <td>
> +            <p> A DHCP implementation based on <a
> +              href="http://www.faqs.org/rfcs/rfc2131.html">RFC 2131</a>. Apache
DHCP
> +              helps configure hosts using configuration information stored in the
> +              Apache Directory backing store.</p>
> +          </td>
> +        </tr>
> +      </table>
> +    </section>
> +  </body>
>  </document>
> 
> 

Mime
View raw message