| Package | Description |
|---|---|
| ca.randolf.net.cs |
These are Client/Server internet I/O classes that encapsulate multiple sets of streams over a single Socket connection (the use of TLS/SSL Sockets is strongly encouraged, but not required). A few key advantages with these classes is that server Operating Systems ultimately don't need to be configured to support as many socket connections, initialization/authentication steps don't need to be repeated (as may normally be the case when opening additional sockets), and built-in compression can help to reduce bandwidth requirements.
|
| Class and Description |
|---|
| Iceberg
The Iceberg class is the encapsulation of a portion of data, similar to a
frame (or packet) of data (which is normally stored in compressed form).
|
| IcebergException
An IcebergException occurs if a problem is encountered with the data (e.g.,
the compressed data is corrupt, the length header field doesn't match the
actual size of the data, etc.).
|
| Lake
The Lake class handles the details of communications in a standard way for
both the client and the server.
|
| River
The River class is connected to the Lake and provides a collection of
methods for accessing both the RiverInputStream and RiverOutputStream, and
various protocol-specific functions designed for specific communication over
through the Streams.
|
| RiverInputStream
The RiverInputStream class provides InputStream-like methods for receiving
data.
|
| RiverOutputStream
The RiverOutputStream class provides OutputStream-like methods for sending
data.
|
| Waterfall
The Waterfall interface must be implemented by call-back classes that will
be called by a Lake object when a new River is received from a remote host.
|