Java Tip 6: Java development and testing without a network

One approach to testing applets involving multiple machines and network accesses on your home PC.

By John D. Mitchell, JavaWorld.com, 04/01/96

So, got my first applets working and the occasional application. Then came networking. I developed a browsing system for our intranet, so that all users could view the weather data available. Now this data ranges from raw observations through to GIFs of numerical model products. This data also resides on many different machines. Some on HP workstations, some on the IBM mainframe and a little on PCs. It was easy to build a system of HTML pages that resided on my HP but loaded graphics from other machines. It was also quite easy to pull data off the IBM and present it as pre-formatted text on a HTML page.

Now this worked well for a while. But as the Java got a bit easier, I started pulling the data in from other machines and started manipulating it (overlays, scaling, color changes). This worked OK. However, I do a lot of my work at home as well. The Java code development was OK. But got to trying to use the Borland Debugger and found out you really do need TCP/IP on the machine and working. Also, found I could do with a Web server on the home machine for testing applets. I'm using Win95 at home and at work, and I found the TCP/IP very easy to use on the work machine.

So I tried to set up TCP/IP at home, but it wouldn't go. I found I needed either a modem or a network card. I have neither at home. Got to work the next day and "borrowed" a network card, a standard SMC Ethernet adaptor. Took that home, slapped it into the machine and got the networking working no problem. Got it down to just TCP/IP loaded (Win95 installs IPX/SPX as well, just remove it). In the TCP/IP setup, I gave my home machine 151.170.1.101 for the IP number. My host file is shown below:

# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
127.0.0.1       localhost   
151.170.1.101   techie      # My work PC
151.170.1.101   pthp        # My HP 712
151.170.1.101   atlas       # Satellite Imagery HP 712
151.170.1.101   fr0400      # Text forecasts HP 712
151.170.1.101   fr0700      # Mesoscale model products HP 712
151.170.1.101   vulcan      # Limited Area Model products HP 712

With this setup, I installed a HTTP daemon (settled on NCSA's) and told it the machine was called techie. This is the same as my work machine. I setup a file structure in the root directory of the HTTPd so that I could browse like I can at work.

For example, my home page at work is kept on my HP pthp. The URL is: http://pthp/bob/home.html. This page also loads a graphic from my PC at work, techie with the line:

<IMG SRC="http://techie/status/recent.gif">

With the setup I now have at home it is possible to mirror this behavior with the above HOSTS file. In my HTDOCS directory for the HTTPd I have two directories, bob and status:

Free Download - 5 Minute Product Review. When slow equals Off: Manage the complexity of Web applications - Symphoniq

Free Download - 5 Minute Product Review. Realize the benefits of real user monitoring in less than an hour. - Symphoniq