Network Computing with Java
Table of Content (Network Computing with Java and Misc topics)
Networking
- Connecting to a Server
- Implementing Servers
- Retrieving Information from a Remote Site
- Sending Information to the Server
- CGI Scripts
- Completing the Mail-Order Applet
- Harvesting Information from the Web
- Connecting to a Gopher Site
- Applet Security
- Proxy Server
- Socket Sockets
- Extendable Socket and ServerSocket
- The design, rationale, and how to do it.
- Socket Options
- New methods to support popular BSD-style options
in the java base classes, (and subclasses can
define their own)
- Socket Exceptions
- New subclasses of SocketException for finer
granularity of handling network errors
- Summary
- Questions
Java Remote Method Invocation (RMI)
- What is RMI
- Learning RMI by Example
- Getting Started Using RMI
- Write The HTML and Java Source Files
- Define a Remote Interface
- Write an Implementation Class
- Write an Applet that Uses the Remote Service
- Write the Web Page that Contains the Applet
- Compile and Deploy Class Files and HTML Files
- Compile the Java Source Files
- Generate Stubs and Skeletons
- Move the HTML File to the Deployment Directory
- Set Paths for Runtime
- Start the Remote Object Registry, Server, and
Applet
- Start the RMI Bootstrap Registry
- Start the Server
- Run the Applet
- RMI System Architecture
- Overview
- Architectural Overview
- The Stub/Skeleton Layer
- The Remote Reference Layer
- The Transport Layer
- Thread Usage in Remote Method Invocations
- Garbage Collection of Remote Objects
- Dynamic Class Loading
- Security
- Configuration Scenarios
- RMI Through Firewalls Via Proxies
- Client Interfaces
- The Remote Interface
- The RemoteException Class
- The Naming Class
- Server Interfaces
- The RemoteObject Class
- The RemoteServer Class
- The UnicastRemoteObject Class
- The Unreferenced Interface
- The RMISecurityManager Class
- The RMIClassLoader Class
- The LoaderHandler Interface
- Table of Contents Page v 5.8 The RMISocketFactory
Class
- The RMIFailureHandler Interface
- The LogStream Class
- Stub and Skeleton Compiler
- Registry Interfaces
- The Registry Interface
- The LocateRegistry Class
- The RegistryHandler Interface
- Stub/Skeleton Interfaces
- The RemoteStub Class
- The RemoteCall Interface
- The RemoteRef Interface
- The ServerRef Interface
- The Skeleton Interface
- The Operation Class
- Garbage Collector Interfaces
- The Interface DGC
- The Lease Class
- The ObjID Class
- The UID Class
- The VMID Class
Java Beans
- What is Java Beans
- Getting Started
- Beans Development Kit (BDK)
- Example Beans and Online Documentation
- The BeanBox
- Testing Sample Beans
- Creating and Testing the Simplest Bean
- Using the BeanBox to Create an Applet
- Properties
- Simple Properties
- Indexed Properties
- Bound Properties
- Constrained Properties
- Example Beans and Properties
- Events
- WaterEventObject
- WaterSource
- Valve
- Pipe
- Testing WaterSource, Valve, and Pipe
- Example Beans and Events
- Customization
- Customizer Interface
- PropertyEditor Interface
- BeanInfo Interface
- Example Beans and Customization
- Persistence
- What to Save
- Changes and Versioning
- Packaging
- MANIFEST file
- Example
- Additional Jar and Manifest File Information
Java Object Serialization
- System Architecture
- Overview
- Writing to an Object Stream
- Reading from an Object Stream
- Object Streams as Containers
- The ObjectOutput Interface
- The ObjectInput Interface
- The Serializable Interface
- The Externalizable Interface
- Protecting Sensitive Information
- Object Output Interfaces
- The ObjectOutputStream Class
- The writeObject Method
- The writeExternal Method
- Object Input Interfaces
- The ObjectInputStream Class
- The ObjectInputValidation Interface
- The readObject Method
- The readExternal Method
- Class Descriptors
- Inspecting Serializable Classes
- Stream Unique Identifiers
- Versioning of Serializable Objects
- Overview
- Goals
- Assumptions
- Whos Responsible for Versioning of Streams
- Compatible Java Type Evolution
- Type Changes Affecting Serialization
- Object Serialization Stream Protocol
- Overview
- Stream Elements
- Grammar for the Stream Format
- Example
- Security in Object Serialization
- Overview
- Design Goals
- Using transient to Protect Important System
Resources
- Writing Class-Specific Serializing Methods
- Encrypting a Bytestream
- Exceptions In Object Serialization
////////
Info ...
rmiregistry - The Java Remote Object Registry
The rmiregistry command starts a remote object registry on the
specified port on the current host.
SYNOPSIS
rmiregistry [port]
DESCRIPTION
The rmiregistry command creates and starts a remote object
registry on the specified port on the current host.
If port is omitted, the registry is started on port 1099. The
rmiregistry command produces no output and is
typically run in the background. For example:
start rmiregistry
A remote object registry is a bootstrap naming service which is
used by RMI servers on a host to bind remote
objects to names. Clients can then look up remote objects and
make remote method invocations.
The registry is typically used to locate the first remote object
on which an application needs to invoke methods.
That object in turn will provide application-specific support for
finding other objects.
The methods of the java.rmi.registry.LocateRegistry class are
used to get a registry operating on a
particular host or host and port.
The URL-based methods of the java.rmi.Naming class operate on a
registry and can be used to look up a
remote object, bind a simple (string) name to a remote object,
rebind a new name to a remote object (overriding
the old binding), unbind a remote object, and list the URLs bound
in the registry.