lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Binary distribution: an evaluation.


From: Robert Bonomi
Subject: Re: LYNX-DEV Binary distribution: an evaluation.
Date: Fri, 6 Dec 1996 14:51:05 -0600 (CST)

+ Date: Fri, 6 Dec 1996 15:17:44 +0400 (GMT-4)
+ From: Duncan Hill <address@hidden>
+ Subject: Re: LYNX-DEV Binary distribution: an evaluation.
+ Sender: address@hidden
+ 
+ On Fri, 6 Dec 1996, Al Gilman wrote:
+ 
+ > If the names are
+ > 
+ >     ftp1.ottawa-ca.browser.org
+ >     ftp2.ottawa-ca.browser.org
+ 
+ >     ftp.barbados.browser.org #deprecated
+ >     ftp.denmark.browser.org
+ >     ...
+ 
+ If we get a mirrors text file up, then we can say where each ottawa-ca
+ is..ie, ftp1 is onet etc..

there is -nothing- that prevents use of 'longer' names (where necessary or
desirable) either, to wit:
        
        ftp.via-onet.ottawa-ca.browser.org
        ftp.via-istar.ottawa-ca.browser.org

Of course, given that these machines are listed on A WEB PAGE, and probably
accessed that way, rather than via 'raw' FTP, one can put most of the 
necessary info in the _text_ of the anchor, rather than having to rely on
it all being in the -name- of the machine.

Methinks a FORM for downloading the 'latest and greatest' version would
be a good idea.  *especially* for binaries.   radio button for which O/S,
another set for supported options (e.g. curses/ncurses/slang), and one more
set for the "preferred" server to fetch from (the text on each server
indicates 'where', and 'connected via', if relevant).  The cgi-bin constructs
a 'minimal' page and fires back:

        You have requested LYNX for ______ (O/S), with the following options:
                 __________
                 __________
                 __________
                 (etc.)

   download  _the_complete_executables_package_
                         _the_instructions_only_
                         _executables_and_source_

The links point to a site where the requested info exists.  which may, or
*may*not* be the one the user requested.  (If the resource -does- exist on
that site, their preference should be honored :)  You get the idea. 
_Anybody_ can 'register' a site, by simply sending in a 'list' of the
configurations they support, and the filenames under which they can be found
on their machine.  If the FORM itself is generated on-the-fly, by a cgi-bin,
then the thing is -entirely- a "look Ma, no hands" operation on the central
server.  The assorted sites simply send in the 'info' files, via e-mail to a
specified address, or by non-anon FTP, or some other method.


;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]