Update old net.sw entry to avoid confusion by the reader.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84603 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Ralf S. Engelschall
2000-02-10 16:38:57 +00:00
parent b5f690162c
commit 5b789782bf

View File

@ -354,14 +354,13 @@ drwxrwxr-x 12 netsw users 512 Aug 3 20:15 Typesetting/
drwxrwxr-x 10 netsw users 512 Jul 9 14:08 X11/ drwxrwxr-x 10 netsw users 512 Jul 9 14:08 X11/
</PRE><P> </PRE><P>
In July 1996 I decided to make this 350 MB archive public to the world via a In July 1996 I decided to make this archive public to the world via a
nice Web interface (<A HREF="http://net.sw.engelschall.com/net.sw/"><CODE> nice Web interface. "Nice" means that I wanted to
http://net.sw.engelschall.com/net.sw/</CODE></a>). "Nice" means that I wanted to offer an interface where you can browse directly through the archive hierarchy.
offer a interface where you can browse directly through the archive hierarchy.
And "nice" means that I didn't wanted to change anything inside this hierarchy And "nice" means that I didn't wanted to change anything inside this hierarchy
- not even by putting some CGI scripts at the top of it. Why? Because the - not even by putting some CGI scripts at the top of it. Why? Because the
above structure should be later accessible via FTP as well, and I didn't above structure should be later accessible via FTP as well, and I didn't
want any Web or CGI stuuf to be there. want any Web or CGI stuff to be there.
<P> <P>
<DT><STRONG>Solution:</STRONG> <DT><STRONG>Solution:</STRONG>
@ -390,7 +389,7 @@ The <CODE>DATA/</CODE> subdirectory holds the above directory structure, i.e. t
real <STRONG><EM>net.sw</EM></STRONG> stuff and gets automatically updated via real <STRONG><EM>net.sw</EM></STRONG> stuff and gets automatically updated via
<CODE>rdist</CODE> from time to time. <CODE>rdist</CODE> from time to time.
The second part of the problem remains: how to link these two structures The second part of the problem remains: how to link these two structures
together into one smooth-looking URL tree? We want to hide the <CODE>DATA/</CODE> together into one smooth-looking URL tree? We want to hide the <CODE>DATA/</CODE>
directory from the user while running the appropriate CGI scripts for the directory from the user while running the appropriate CGI scripts for the
various URLs. various URLs.