You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by ha...@apache.org on 2002/05/29 22:00:30 UTC

cvs commit: jakarta-avalon-apps/site/src/xdocs todo.xml

hammant     02/05/29 13:00:29

  Modified:    site/src/xdocs todo.xml
  Log:
  spelling mistakes
  
  Revision  Changes    Path
  1.4       +7 -7      jakarta-avalon-apps/site/src/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-apps/site/src/xdocs/todo.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- todo.xml	18 Apr 2002 20:18:21 -0000	1.3
  +++ todo.xml	29 May 2002 20:00:29 -0000	1.4
  @@ -17,7 +17,7 @@
         We're looking for people to help out and write or port some of these services.
         If it's a port of an existing service, it's original license should be honoured.
         For example if you are porting C source from the BSD operating system to Java,
  -      it's probably true that you should keep the block as BSD licensed.  Naturely
  +      it's probably true that you should keep the block as BSD licensed.  Naturally
         we'd prefer to see original code written that's Apache software licensed.  Of course
         there is plenty of room for multiple implementations of a given service/daemon.
       </p>
  @@ -50,9 +50,9 @@
     <s1 title="TCP/IP Daemons (as per Unix)">
       <p>
         RFC compliance is the key here.  Porting BSD source to Java might be a route
  -      to delivering these server apps. In some cases theoure could be multiple block
  +      to delivering these server apps. In some cases there could be multiple block
         implementations (One NTP block could look at the PC's local clock, another
  -      delagates to another NTP server, they may even share code and be in the same
  +      delegates to another NTP server, they may even share code and be in the same
         .bar file).
       </p>
         <s2 title="Domain Name Service">
  @@ -61,9 +61,9 @@
           </p>
           <p>
             DNS in Java has been done already.  See <link href="http://sourceforge.net/projects/dnsjava/">
  -          http://sourceforge.net/projects/dnsjava/</link>.  This is LGPL licnsed software so could not
  +          http://sourceforge.net/projects/dnsjava/</link>.  This is LGPL licensed software so could not
             be hosted by Apache if a port were undertaken.  It might be best to start afresh as there are
  -          so many possibilites for abstractions and configurable concepts (forwarding DNS impls, DNSlet,
  +          so many possibilities for abstractions and configurable concepts (forwarding DNS impls, DNSlet,
             Some using persistence stores, some using databases
           </p>
         </s2>
  @@ -88,7 +88,7 @@
         </s2>
         <s2 title="Network Time Protocol (NTP)">
           <p>
  -          The service that Internet based computers use to syncronise their clocks.  Very useful
  +          The service that Internet based computers use to synchronise their clocks.  Very useful
             for secure and time critical services.
           </p>
         </s2>
  @@ -99,7 +99,7 @@
           <p>
             See <link href="http://www.openssh.org/java.html">
             http://www.openssh.org/java.html</link> for details about available java tools.  Mindterm, listed
  -          there, would be a good candiate, but it forked and went in two directions (1) Commercial/closed (2)
  +          there, would be a good candidate, but it forked and went in two directions (1) Commercial/closed (2)
             GPL.  The latter is not allowed to import ASF licensed code ("Block" being an example) so could
             not be ported.  A from scratch impl would be best here.
           </p>
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>