Java Doc for ImageServer.java in  » 6.0-JDK-Modules » Java-Advanced-Imaging » com » sun » media » jai » rmi » Java Source Code / Java DocumentationJava Source Code and Java Documentation

• Additional setRenderedSource() and setRenderableSource methods are provided to inform the server as to the source of image data for this image. Sources may be set either from a RenderedImage that is copied over to the server, or from a graph of RenderedOp objects indicating an abstract imaging chain to be instantiated using the server's OperationRegistry.
• All methods throw RemoteException. This is a requirement of any Remote interface.
• The getTile() method does not return a reference to a `live' tile; instead it returns a client-side copy of the server image's tile. The difference is moot since the server image is immutable.

 ImageServer im;
 im = java.rmi.Naming.lookup("//host:1099/javax.media.jai.RemoteImageServer");
 

The hostname and port will of course depend on the local setup. The host must be running an rmiregistry process and have a RemoteImageServer listening at the desired port.

This call will result in the creation of a server-side JAIRMIImageServer object and a client-side stub object. The client stub serializes its method arguments and transfers them to the server over a socket; the server serializes it return values and returns them in the same manner.

This process implies that all arguments and return values must be serializable. In the case of a RenderedImage source, serializability is not guaranteed and must be considered on a class-by-class basis. For RenderedOps, which are basically simple nodes connected by ParameterBlocks, serializability will be determined by the serializabiility of the ultimate (non-RenderedOp) sources of the DAG and the serializability of any ad-hoc Object parameters held in the ParameterBlocks.

The return values of the getData(), copyData(), and getTile() methods are various kinds of Rasters; at present, Java2D does not define serialization on Rasters. We will either need to add this feature to Java2D or else coerce the server-side Rasters into a serializable subclass form. In any case, we will want to implement lossless (and possibly lossy) compression as part of the serialization process wherever possible.
See Also:   java.rmi.Remote
See Also:   java.rmi.RemoteException
See Also:   java.awt.image.RenderedImage

The class of the returned object will vary as a function of the nature of the operation.

The created RenderedImage may have a property identified by the String HINTS_OBSERVED to indicate which RenderingHints (from the RenderContext) were used to create the image. In addition any RenderedImages that are obtained via the getSources() method on the created RenderedImage may have such a property.
Parameters:
  renderContext - the RenderContext to use to produce the rendering. a RenderedImage containing the rendered data.

If w == 0, it will be taken to equal Math.round(h*(getWidth()/getHeight())). Similarly, if h == 0, it will be taken to equal Math.round(w*(getHeight()/getWidth())). One of w or h must be non-zero or else an IllegalArgumentException will be thrown.

The created RenderedImage may have a property identified by the String HINTS_OBSERVED to indicate which RenderingHints were used to create the image. In addition any RenderedImages that are obtained via the getSources() method on the created RenderedImage may have such a property.
Parameters:
  w - the width of rendered image in pixels, or 0.
Parameters:
  h - the height of rendered image in pixels, or 0.
Parameters:
  hints - a RenderingHints object containg hints. a RenderedImage containing the rendered data.

The class of the returned object will vary as a function of the nature of the operation. For rendered and renderable two- dimensional images this should be an instance of a class which implements java.awt.Shape. The region over which the data of two renderings of thisoperation may be expected to be invalid or nullif there is no common region of validity.