Ships from: Fort Worth, TX
Usually ships in 1-2 business days
Ships from: Chatham, NJ
Usually ships in 1-2 business days
Ships from: San Marino, CA
Usually ships in 1-2 business days
Java developers in general and EJB developers in particular need to master RMI (Remote Method Invocation) technology if they are to write distributed, enterprise-strength applications that communicate effectively with remote applications and devices even under heavy traffic. In this new book, an award-winning and internationally recognized Java expert shows experienced Java and EJB developers how to utilize the full capabilities of RMI to write fast, efficient, fault-tolerant, and flexible applications. This book is a true programming tutorial that provides sophisticated examples that developers can directly implement and customize—a huge timesaving feature!
We begin by looking at the basic definition of what a client/server architecture is. It is very likely that you already have some understanding of what client/server architecture is all about; however, let's start by reviewing the basic definition to ensure that you have a well-defined base to work with.
We then take a look at the most common concepts that are involved in creating a distributed architecture, such as RMI. I have identified what I feel are the core parts of just about every distributed architecture, and when we get to the specifics of RMI, you will see how different parts of the RMI design relate to those basic building blocks.
In the last part of this introductory chapter, I show you a couple of different client/server architectures and give you a brief overview of how they have implemented the concepts that have been described in this chapter. This will make it much easier to see how RMI fits in and how it differs from other architectures.
(If you're tempted to skip directly to Chapter 2, first take a brief look at the sections under "Basics of Networked Computing," as I will be referring to those concepts when I describe the RMI architecture.)
Client/Server Basics
Let's begin by looking at what a client/server architecture is and define the notions of client and server. Most people have an intuitive idea of what they are, but with the introduction of the Internet, the words client and server are often used in different contexts. Their meaning therefore slightly differs depending on usage.
Once you have a clear picture of what a client/server architecture really is, we take a brief look at the reasons you might want to use one and whether or not there are alternatives.
The Definition of Client and Server
If you look at the main characteristics of clients and servers, you can use the following definition, which works in most cases: A server is a software program that provides one or more services that can be used by zero or more clients. A client is something that uses at least one service provided by at least one server...
Overview
Java developers in general and EJB developers in particular need to master RMI (Remote Method Invocation) technology if they are to write distributed, enterprise-strength applications that communicate effectively with remote applications and devices even under heavy traffic. In this new book, an award-winning and internationally recognized Java expert shows...