Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

edu.emory.mathcs.util.remote.io.* (6)edu.emory.mathcs.util.remote.io.server.* (4)
edu.emory.mathcs.util.remote.io.server.impl.* (2)edu.emory.mathcs.util.remote.server.* (2)
edu.emory.mathcs.util.remote.server.impl.* (1)

edu.emory.mathcs.util.remote: Javadoc index of package edu.emory.mathcs.util.remote.


Package Samples:

edu.emory.mathcs.util.remote.server.impl: Utilities extending several traditional APIs to work across the network using RMI.  
edu.emory.mathcs.util.remote.io.server: I/O streams over RMI.  
edu.emory.mathcs.util.remote.io
edu.emory.mathcs.util.remote.io.server.impl
edu.emory.mathcs.util.remote.server

Classes:

RemoteInputStream: Serializable input stream that reads from an input stream on a remote host, using RMI. Since RMI itself can be enabled over various protocols and socket factories, this class allows to tunnel byte streams through a variety of protocols. For example, if used with RMIX, it is possible to tunnel streams via SOAP/HTTP. Typical usage pattern is to create the instance at the server side and then send it to the client via RMI. For example: InputStream getRemoteStream() throws RemoteException { InputStream source = ...; return new RemoteInputStream(source); }
RemoteOutputStream: Serializable output stream that writes to an output stream on a remote host, using RMI. Since RMI itself can be enabled over various protocols and socket factories, this class allows to tunnel byte streams through a variety of protocols. For example, if used with RMIX, it is possible to tunnel streams via SOAP/HTTP. Typical usage pattern is to create the instance at the server side and then send it to the client via RMI. For example: OutputStream getRemoteStream() throws RemoteException { OutputStream sink = ...; return new RemoteInputStream(sink); }
RemoteProcess: Serializable handle to a native process running on a remote machine. Communicates via RMI with the process handle at the server side. Since the handle is serializable, it can be sent over RMI (e.g. returned from a remote call). For example: RemoteProcess getRemoteProcess() throws RemoteException { // locate (or start) nativeProcess // ... return new RemoteProcess(nativeProcess); }
RemoteProcessSrvImpl: Server-side remote handle to the native process.
RemoteOutputStreamSrvImpl: Server-side remote handle to an output stream.
RemoteProcessSrv: Server interface to the remote native process.
RemoteOutputStreamSrv: Server interface to the remote output stream.
RemoteInputStreamSrvImpl: Server-side remote handle to an input stream.
RemoteInputStreamSrv: Server interface to the remote input stream.

Home | Contact Us | Privacy Policy | Terms of Service