Running the Example
To
run both the RestoPeer and HungryPeer applications you must create
two separate directories. Place the
HungryPeer.java file in one directory, and the
RestoPeer.java file in another directory. Each
source file is compiled as we discussed in Chapter 3. The applications must exist in separate
directories so that their configuration information will remain
separate.
Let’s compile and start the HungryPeer first and see what happens:
piccolo%cd ch04/HungryPeerpiccolo%javac HungryPeer.javapiccolo%java HungryPeerSecurity initialization in progress. This will take 10 or more seconds ... Attempting to discover the RestoNet Peergroup Sorry could not find the RestoNet Peergroup
When you start the application, you’re first presented with the configurator. After filling it out, you’ll see the output listed above. The HungryPeer application attempts to discover the RestoNet peergroup and aborts after 3 tries (a total of 30 seconds). This is what we’d expect, since the RestoPeer application has not yet created the RestoNet peergroup.
Oddly enough, when you run this example you may find instead that the HungryPeer has jointed the RestoNet peergroup. There is no black magic here; this just means that someone else has already run the RestoPeer service on your JXTA network. Similarly, once the HungryPeer has found the RestoNet peergroup, it caches this information; if you rerun the HungryPeer at a later point, it will report that it has found the RestoNet peergroup even ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access