[HECnet] Lynx

[sampsa at mac.com]

Maybe add a new URL handler like decnet://host/file/ that then uses the file system to retrieve the file?

Just an idea..Modifying the file:// handler code would be the easiest solution I should think, however.


sampsa






On 29 Jan 2013, at 17:45, Johnny Billquist <bqt at softjar.se> wrote:

On 2013-01-29 16:02, Erik Olofsen wrote:
Well from this link

http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html

it doesn't seem to be straightforward...

That sounds silly. All that is needed is just to get the damned file specification literally down to the function that opens the file, and you are done.

	Johnny


Erik

On Tue, Jan 29, 2013 at 04:45:18PM +0200, sampsa at mac.com wrote:
I wonder how hard that would be to change?


sampsa






On 29 Jan 2013, at 16:29, Erik Olofsen <e.olofsen at xs4all.nl> wrote:

Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...

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