Now that UDI's (Universal Document Identifiers) and things like gopher,
wais, www, alex, ... are in, I am wondering if the following could
be implemented for listearn and listserv :
 
Make a file via a filelist available, while the file is stored on another
listserv/earn.  If such a file is requested,  the first listearn/serv
will forward the request to the listserv/earn where the file is actually
stored.  This listearn/serv will send the file to the user.
 
e.g. in a filelist (or the fileid) I would have something like
 myfile test .... searn listserv  ... hisfile test
 
If a user requests the file 'myfile test' on my listserv, my listserv
will forward the request to listserv at searn, where the file 'hisfile test'
will be send to the requesting user.
 
I think this could be usefull in some places :
 
  - I have a package xyz, that uses package zyx form [log in to unmask]
    For some reason, I can or do not want to store package zyx on my
    listserv.  With the new future and a user requesting my package
    xyz, the user will also receive the package zyx.
 
A special control procedure would check every month that all the files
on other listserv/earn still exists.  Maybe it is not even necessary
to request that the other server must be a listearn/listserv, it can
be another server that understands the rules (e.g. it could be a server
pulling files from tape, or it could be a server FTP-ing files).
 
-Herman-