|
Difference between
version 22
and
version 15:
| Lines 17-22 were replaced by lines 17-19 |
| - ##''Subcribe'': The server pushes new data as it is received to the sink application's designated |
| - channel map. All data is sent to the application in a continuous stream regardless of whether the application can keep up. |
| - ##''Monitor'': The server pushes new data as it is received to the sink application's designated |
| - channel map. The server skips ahead, dropping data if necessary, if the sink application gets too far behind in its processing. |
| - ##''Request'': |
| - * |
| + ##''Subcribe'': The server pushes new data as it is received to the sink application's designated channel map. All data is sent to the application in a continuous stream regardless of whether the application can keep up. |
| + ##''Monitor'': The server pushes new data as it is received to the sink application's designated channel map. The server skips ahead, dropping data if necessary, if the sink application gets too far behind in its processing. |
| + ##''Request'': The sink application sends the server a channel map containing the name of the channel, timestamp, and duration of the requested data. The server responds by returning the channel map with the requested data filled in. |
| At line 25 added 4 lines. |
| + In REAP, we will start by designing a an API for RBNB operations and an ''RBNBSink'' actor that can operate in all three modes of using channel maps. We will build the actor based on the defined APIs. This is discussed in [RBNB Sink Actor Design page|RBNBSinkActorDesignAndAPI]. |
| + |
| + \\ |
| + |
Back to Ring Buffered Network Bus,
or to the Page History.
|
