|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||
See:
Description
| Interface Summary | |
| DataSink | A data sink is the ending point of a pipe. |
| DataSource | A data source is the starting point of a pipe. |
| FapConstants | Constants used by FAP service. |
| FapService | A distributed service implementing Filter-and-Pipe (FAP) architectural pattern. |
| Filter | Filter is one component that processes one or more incoming data streams and produces another one. |
| SinkChannel | A sink channel is for filter to send data. |
| SourceChannel | A source channel is for filter to receive data. |
| Class Summary | |
| DirectPipe | A direct pipe has no buffer inside. |
| FapClientService | Implementation of Filter-and-Pipe (FAP) service. |
| InputPort | An input port of a sink filter to a pipe. |
| LocalSinkChannel | The data sink of this channel is on the local site. |
| LocalSourceChannel | The data source of this channel is on the local site. |
| OutputPort | An output port of a source filter to a pipe. |
| Pipe | A pipe consists of a pair of channels: A writable sink channel and a readable source channel. |
| PipeFactory | The factory produces new pipe objects. |
| Port | A port is a connection point between filters and pipes. |
| RemoteSinkChannel | The data sink of this channel is on a remote site. |
| RemoteSourceChannel | The data source of this channel is on a remote site. |
| SolarFapService | Implementation of Filter-and-Pipe (FAP) service. |
| Exception Summary | |
| FapException | An exception thrown by Filter-and-Pipe (FAP) service. |
Contains FAP (Filter-and-Pipe) service and related classes. A FAP model is ideal for data-flow processing, either distributed or localized. It contains application-specific filters and customized pipes (flow control, for instance).
|
|||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||||