Book Image

Learning Network Programming with Java

Book Image

Learning Network Programming with Java

Overview of this book

Network-aware applications are becoming more prevalent and play an ever-increasing role in the world today. Connecting and using an Internet-based service is a frequent requirement for many applications. Java provides numerous classes that have evolved over the years to meet evolving network needs. These range from low-level socket and IP-based approaches to those encapsulated in software services. This book explores how Java supports networks, starting with the basics and then advancing to more complex topics. An overview of each relevant network technology is presented followed by detailed examples of how to use Java to support these technologies. We start with the basics of networking and then explore how Java supports the development of client/server and peer-to-peer applications. The NIO packages are examined as well as multitasking and how network applications can address practical issues such as security. A discussion on networking concepts will put many network issues into perspective and let you focus on the appropriate technology for the problem at hand. The examples used will provide a good starting point to develop similar capabilities for many of your network needs
Table of Contents (16 chapters)
Learning Network Programming with Java
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Multithreaded server overview


The chief advantage of a multithreaded server is that long-running client requests will not block the server from accepting other client requests. If a new thread is not created, then the current request will be processed. It is only after the request has been processed that new requests can be accepted. Using a separate thread for a request means that connections and their associated requests can be processed concurrently.

When using a multithreaded server, there are several of ways of configuring the threads as follows:

  • Thread-per-request

  • Thread-per-connection

  • Thread-per-object

In the thread-per-request model, each request that arrives at the server is assigned a new thread. While this is a simple approach, it can result in the creation of a large number of threads. In addition, each request will often mean that a new connection will be created.

This model works nicely in an environment where the previous client request does not need to be retained. For example...