| |
I just wrote a really really basic web server for my atari 800.
It listens on it's serial port (9600 baud) for a CD, and spits
out the html page and drops DTR. The serial port is connected
to an old CS-210 terminal server which is set to listen on
port 23. So, if you connect to port 23 on the terminal server
it spits out the web page. Unfortunately there is no way
to configure the TS to listen to port 80 so I will need to
configure an address translator in front of it.
For now you can connect to it (via telnet or msie):
http://atari800.kl.net:23
Netscape seems to block port 23 for some reason but IE works.
At 9600 baud and around 220 characters for the page it should support
3-4 hits per second!
KL
|
|
Message has 6 Replies:
 | | Re: atari 800 web server
|
| (...) That's awesome! (...) It's a security thing. Netscape doesn't let you access ports it knows a protocol for via a different protocol. This started with Navigator 3.0, I believe. (I think the security implications are limited to "might help (...) (25 years ago, 19-Mar-00, to lugnet.off-topic.geek)
| | | Re: atari 800 web server
|
| (...) It is now ready for prime time. I figured out how to get the terminal server to listen to port 80, and it doesn't bark garbage characters on that port. I moved it to work so it has some real bandwidth to play with. (URL)KL (25 years ago, 20-Mar-00, to lugnet.off-topic.geek)
| | | Re: atari 800 web server
|
| I just have to ask: Is there any actual USE for this thing other than the novelty factor? (reason enough for doing it, of course) What's the oldest iron known to be interfaced to the net this way? The dumbest (most limited CPU) The smallest? (...) (25 years ago, 25-Mar-00, to lugnet.off-topic.geek)
|
25 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
