Running Standalone Over AppleTalk

• To: janson2@ibm.net (james anderson)
• Subject: Running Standalone Over AppleTalk
• From: "John C. Mallery" <jcma@ai.mit.edu>
• Date: Mon, 30 Dec 1996 13:59:57 -0500
• Cc: www-cl@ai.mit.edu, cvince@ai.mit.edu, bug-mac-cl-http@ai.mit.edu
• In-Reply-To: <v01540b00aeecc90d394c@[139.92.6.122]>
• Sender: owner-www-cl@ai.mit.edu

James,

1. When reporting problems, it is helpful to know your hardware and software
configuration. MacTCP is different from OPenTransport.

2. Remember that you still have to tell MacTCP or OpenTransport the IP
address of your machine. The standalone procedure allows you to use
a name rather than an ip address to refer to your server. The standalone procedure works is by assigning IP addresses to domain names (and CNAMES) in the hosts file that you keep in your system folder.

This works fine for many of us under MACTCP and OpenTransport 1.1.1 or higher.
If you are having difficulties, please try to identify the unclear step or
the missing information from the instructions for standalone configuration
so that we can improve the documentation.

3. Your DNS based approach is a good idea that is on the list
for more sophisticated standalone operation. The main feature is that
it will allow an AppleTalk only network to use domain names without having
to define the IP <=> domain name mappings for every host on the net in every
host's host file in the system directory.

4.The standalone approach really comes into its own when running a proxy server that can deliver remote content even though you are disconnected.  This can be combined with asynchronous demand  caching via the web walker to achieve a very nice mobility environment and a nice proxy example.

• Re: (still) can't start CL-HTTP
• From: janson2@ibm.net (james anderson)

• Prev: Re: (still) can't start CL-HTTP
• Next: run cl-http behind firewall?
• Index(es):
  • Main
  • Thread