[HECnet] Lynx

In the meantime I have a working Lynx 2.8.7 and studied the url parsing in the debugger. When specifying a VMS file name, it is first converted to a valid url; then there are many url checks, and of course when the file needs to be opened, it is converted back to a VMS file specification. Interestingly (is it a feature or a bug?), $ lynx file://localhost/rullfs:/.www/simple.html or just $ lynx /rullfs:/.www/simple.html works, because it is assumed that the the first part is a device name, without a colon, on localhost. But because it already contains a colon, it is converted to a host specification... I've not checked yet what happens if http:// is part of the url, and what needs to be done if there were an html object at the remote host. Erik On Tue, Jan 29, 2013 at 04:40:49PM +0100, Johnny Billquist wrote: On 2013-01-29 15:29, Erik Olofsen wrote: Yes indeed - unfortunately it doesn't work because Lynx does not allow a host:: name as part of the url... I suspected as much from the comments in the url you sent. Seems silly, though. What happens if you just say "file://mim::info.txt" ? (I must admit that I'm slightly confused on how many slashes are appropriate...) Johnny Erik On Tue, Jan 29, 2013 at 03:26:01PM +0100, Johnny Billquist wrote: On 2013-01-29 14:53, Erik Olofsen wrote: If we may use an url such as mim::something.html, which would normally be a file:// there would be some basic functionality I think? Right, since that is basically just using the file: transport/protocol. The fact that files can be accessed transparently over DECnet makes it possible to access documents "over DECnet". Depending on how the parsing/handling of the url for something in the file: domain is done, this might actually work straight away. Johnny Erik On Tue, Jan 29, 2013 at 02:04:39PM +0100, Johnny Billquist wrote: On 2013-01-29 13:44, Erik Olofsen wrote: HECnetters, Is anyone interested in using Lynx on HECnet? Using node names in the url is not possible; some information is here: http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html On my Alpha with VMS 6.1, I'm able to compile Lynx version 2.3. It seems that the latest version, 2.8.7, does not compile under VMS 8.3. Perhaps I'm going to have a look at the old sources; perhaps I'm going to do something more useful... Well, the basic "problem" is that there is no http object defined in DECnet, nor any equivalent to the http protocol, so how would you expect it to work? DECnet is not IP, nor TCP. Johnny