and run the
programs in this chapter. Now edit the files to remove all of the buffering for
the input and output, then compile and run them again to observe the results.
a server that asks for a password, then opens a file and sends the file over
the network connection. Create a client that connects to this server, gives the
appropriate password, then captures and saves the file. Test the pair of
programs on your machine using the
(the local loopback IP address
produced by calling
the server in Exercise 2 so that it uses multithreading to handle multiple
so that output flushing doesn’t occur and observe the effect.
to produce an applet that is a password-protected gateway to a particular
portion of your Web site.
challenging) Create a client/server pair of programs that use datagrams to
transmit a file from one machine to the other. (See the description at the end
of the datagram section of this chapter.)
challenging) Take the
program and modify it so that when you click on the resulting name it
automatically takes that name and copies it to the clipboard (so you can simply
paste it into your email). You’ll need to look back at the IO stream
chapter to remember how to use the Java 1.1 clipboard.
With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish.
Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.
Instead of only managing projects organizations do need to manage value!
"Doing the right things" and "doing things right" are the essential ingredients for successful software and systems delivery. Unfortunately, with distributed delivery spanning multiple disciplines, geographies and time zones, many organizations
struggle with teams working in silos, broken lines of communication, lack of collaboration, inadequate traceability, and poor project visibility. This often results in organizations "doing the …