Thanks Johnny.
Steve,
I just got the OS installed late last night, so please be patient as I'll need to go and get the multinet SW and hobbyist license and before I can attempt to connect.
Once I get it all setup I'll send you my IP address and info to test a connection.
thanks.
> Date: Tue, 29 Jan 2013 16:51:05 +0100
> From: bqt at softjar.se
> To: hecnet at Update.UU.SE
> CC: jeep at scshome.net; mholmes10 at hotmail.com
> Subject: Re: [HECnet] New HECnet Area Request
>
> Mike, I'm putting area 39 to your name. Will Steve work for your connection?
>
> Johnny
>
> On 2013-01-29 11:55, Steve Davidson wrote:
> > Mike,
> >
> > Area 39 is available. If you decide to use Multinet Tunnels then configure it to connect to 69.21.253.158 and send me mail with your IP address. If it is a dynamic IP address then I will need to know the domain as well.
> >
> > -Steve
> >
> > ________________________________
> >
> > From: owner-hecnet at Update.UU.SE on behalf of Michael Holmes
> > Sent: Mon 1/28/2013 18:42
> > To: hecnet at Update.UU.SE
> > Subject: [HECnet] New HECnet Area Request
> >
> >
> >
> > Hi all,
> >
> > My alphaserver 800 finally arrived and I'm setting it up now and would like to request a HECNET area so I experiment with connecting to HECNET.
> >
> > I saw a previous message listing available areas and I'd like to request area 39 if its not already spoken for.
> >
> > I finally found a SCSI drive that will work in it and am currently installing VMS 8.3 and DECNET IV on it right now.
> >
> > Hopefully will have it finished tonight and be able work on the HECNET options (router, etc) through the week and weekend.
> >
> > I also have a DEC 3000L and a multia that I'll try to bring back to life sometime later.
> >
> > Thanks
> >
> > Mike
> >
> > Alexandria, VA
> >
> >
> >
>
On 2013-01-29 16:48, sampsa at mac.com wrote:
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.
Yeah. Just grabbing everything after the file://, and (possibly if no more slashes are seen) just pass that whole string down should do it.
Johnny
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
On Jan 29, 2013, at 10:43 AM, Johnny Billquist wrote:
On 2013-01-29 15:36, Brian Schenkenberger, VAXman- wrote:
Johnny Billquist <bqt at softjar.se> writes:
...
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.
There are web servers for VMS and I believe you have one running on RSX.
The problem is not one of http but shipping that http over DECnet. Get
the browser and web server speaking DECnet and you're 99% of the way to
the goal.
Certainly there are web servers for both VMS and RSX. None of them (to my knowledge) speaks DECnet. And then you need some browser that also speaks DECnet, and which agrees on the protocol.
There is a problem with the standard http protocol which makes it slightly tricky with DECnet.
http expects to be able to send empty lines. DECnet don't do that. DECnet sends records, and empty records don't get sent at all. I realized this when looking at the MAIL-11 protocol...
So we'd need to do some changes to the http protocol to adopt it on DECnet...
Johnny
That should be completely trivial. First, you assign an object number (pick a number -- 80 would be an obvious choice). Then you send the data across a DECnet connection. That too is easy. Yes, DECnet sends packets, not just a dumb byte stream. So it has structure, IF you need it. If you don't, just pour the bytes into the packets and send them. Ultrix does that -- its DECnet sockets have both a packet and a stream mode. I'm not entirely sure how stream mode behaves; my guess would be that it just sticks the stream into packets whichever way is convenient.
As for the blank lines, that's not an issue. A blank line is \r\n (or maybe just \n) but it certainly is not a null string. So an HTTP request would live inside a packet that contains the text of the request, WITH the newline characters.
paul
Mike, I'm putting area 39 to your name. Will Steve work for your connection?
Johnny
On 2013-01-29 11:55, Steve Davidson wrote:
Mike,
Area 39 is available. If you decide to use Multinet Tunnels then configure it to connect to 69.21.253.158 and send me mail with your IP address. If it is a dynamic IP address then I will need to know the domain as well.
-Steve
________________________________
From: owner-hecnet at Update.UU.SE on behalf of Michael Holmes
Sent: Mon 1/28/2013 18:42
To: hecnet at Update.UU.SE
Subject: [HECnet] New HECnet Area Request
Hi all,
My alphaserver 800 finally arrived and I'm setting it up now and would like to request a HECNET area so I experiment with connecting to HECNET.
I saw a previous message listing available areas and I'd like to request area 39 if its not already spoken for.
I finally found a SCSI drive that will work in it and am currently installing VMS 8.3 and DECNET IV on it right now.
Hopefully will have it finished tonight and be able work on the HECNET options (router, etc) through the week and weekend.
I also have a DEC 3000L and a multia that I'll try to bring back to life sometime later.
Thanks
Mike
Alexandria, VA
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
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
On 2013-01-29 15:36, Brian Schenkenberger, VAXman- wrote:
Johnny Billquist <bqt at softjar.se> writes:
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.
There are web servers for VMS and I believe you have one running on RSX.
The problem is not one of http but shipping that http over DECnet. Get
the browser and web server speaking DECnet and you're 99% of the way to
the goal.
Certainly there are web servers for both VMS and RSX. None of them (to my knowledge) speaks DECnet. And then you need some browser that also speaks DECnet, and which agrees on the protocol.
There is a problem with the standard http protocol which makes it slightly tricky with DECnet.
http expects to be able to send empty lines. DECnet don't do that. DECnet sends records, and empty records don't get sent at all. I realized this when looking at the MAIL-11 protocol...
So we'd need to do some changes to the http protocol to adopt it on DECnet...
Johnny
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
Well from this link
http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html
it doesn't seem to be straightforward...
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
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
