Java™ Application Development on Linux - Dator

146Chapter 5The Sun Microsystems Java Software <strong>Development</strong> KitExample 5.13 A Java security policy file suitable for the RMI examplegrant {permission java.net.SocketPermission "*:1024-65535", "connect,accept";permission java.net.SocketPermission "*:80", "connect,accept";};5.8.4.2 Our EnvironmentWe have two machines. One, penfold, is our server machine. The other,grovel, is our client machine. To keep things straight in our samples, the shellprompts will have the host names in them.If you are using a JDK that supports the 1.2 RMI specification (and wehope you are—it’s in all current JDKs), you have to give your server and yourclient permission to access the network ports needed to run. By default, theJava runtime will look for a security policy file in the home directory of theuser running the VM. The default name of the file is .java.policy. Example5.13 shows what we suggest you put in this file, at least to run this example.NOTEYou will have to put this in your home directory both on the server and on allclient machines.5.8.4.3 Compiling and Running the ServerOur packages here follow Sun’s suggested naming convention of yourdomain name, reversed, followed by your package names. It so happens thatMr. Schwarz’s domain is called multitool.net (named after his firstbook, Multitool Linux), so we put all of these classes in a package callednet.multitool.RMIDemo.For all of the examples in this section, as well as the following section onbuilding and running the client, assume that our current working directory isthe directory that contains the net directory of our source code.The output you see in Example 5.14 includes the result of running ourclient once. Note that the SessionImpl class doesn’t terminate. It keepsrunning to service clients indefinitely.