Home >> All >> edu >> emory >> mathcs >> util >> [ net Javadoc ]

•	edu.emory.mathcs.util.net.compressed.* (2)	•	edu.emory.mathcs.util.net.inproc.* (3)
•	edu.emory.mathcs.util.net.ssl.* (2)

• edu.emory.mathcs.util.net: Javadoc index of package edu.emory.mathcs.util.net.


Package Samples:

• edu.emory.mathcs.util.net.inproc: Networking-related utility classes.  
• edu.emory.mathcs.util.net.ssl
• edu.emory.mathcs.util.net.compressed

Classes:

• ConnectionPool: Manages a pool of socket connections to a single network endpoint. Pooling enables reusing connections for multiple, unrelated data transfers, and it can be used to implement certain connection-based protocols like HTTP 1.1. Additionally, pooling can aid in controlling network load - limiting the maximum pool size causes excessive connection requests to be enqueued at the client side. The endpoint is represented by a host name and a port number, as well as by an optional client socket factory, specified at the construction time. Client requests connections, use them, then return them to the pool. ...
• InProcServerSocket: Abstraction of a server socket which can be accessed only from within a process. While this class fully adheres to the socket API, it is a server socket that accepts connections only from appropriate "sockets" within the same process. The class can be used to create local in-process bindings within APIs that assume remote access. For instance, when used as an RMI transport, in-process sockets can interconnect local objects while maintaining remote invocation semantics (pass-by-value etc.) yet avoiding security risks associated with network sockets and offering a bit better performance than a loopback ...
• CompressedServerSocketWrapper: Server socket wrapper that enables data compression on top of connections accepted by a specified server socket. The accept method of this class delegates to the underlying server socket and wraps accepted sockets into CompressedSocketWrapper .
• SSLServerSocketWrapper: Wrapper for SSL server sockets which enables to add functionality in subclasses on top of existing, bound SSL server sockets. It is useful when direct subclassing of delegate socket class is not possible, e.g. if the delegate socket is created by a library. Possible usage example is socket factory chaining. This class delegates all socket-related requests to the wrapped delegate, as of JDK 1.4.
• ServerSocketWrapper: Wrapper for server sockets which enables to add functionality in subclasses on top of existing, bound server sockets. It is useful when direct subclassing of delegate socket class is not possible, e.g. if the delegate socket is created by a library. Possible usage example is socket factory chaining. This class delegates all socket-related requests to the wrapped delegate, as of JDK 1.4.
• SSLSocketWrapper: Wrapper for sockets which enables to add functionality in subclasses on top of existing, connected SSL sockets. It is useful when direct subclassing of delegate SSL socket class is not possible, e.g. if the delegate socket is created by a library. Possible usage example is socket factory chaining. This class delegates all socket-related requests to the wrapped delegate, as of JDK 1.4.
• SocketWrapper: Wrapper for sockets which enables to add functionality in subclasses on top of existing, connected sockets. It is useful when direct subclassing of delegate socket class is not possible, e.g. if the delegate socket is created by a library. Possible usage example is socket factory chaining. This class delegates all socket-related requests to the wrapped delegate, as of JDK 1.4.
• InProcSocket: Abstraction of a socket accessible only within a process. While this class fully adheres to the socket API, it is a socket that can only connect to an appropriate "server socket" within the same process.
• CompressedSocketWrapper: Socket wrappper that enables data compression over an established socket connection. The output stream associated with this socket guarantees that flush sends out all the data that has been written so far. Hence, this kind of socket can be used as a transport for request-response-based protocols, like RMI or RPC.
• Connection: Single connection from pool of connections. Every connection has associated connected socket and expiration timeout.
• DecoratingServerSocket: Marker interface that indicates that a server socket is a wrapper for another server socket.
• DecoratingSocket: Marker interface that indicates that a socket is a wrapper for another socket.
• InProcSocketAddress: Represents an address of in-proc socket. Consists of a logical port number.

Home | Contact Us | Privacy Policy | Terms of Service