[kepler-dev] [Bug 3157] New: - RBNBToKepler actors should support all three sink modes
bugzilla-daemon at ecoinformatics.org
Fri Feb 22 15:58:53 PST 2008
Summary: RBNBToKepler actors should support all three sink modes
Component: data access
AssignedTo: barseghian at nceas.ucsb.edu
ReportedBy: barseghian at nceas.ucsb.edu
QAContact: kepler-dev at ecoinformatics.org
RBNBToKepler actors should support all three sink modes: Subscribe, Monitor and
Request. Currently only Request is supported -- RBNBToKepler simulates Monitor
mode with Requests for the newest data in an endless do-while loop, and
RBNBToKepler2 and 3 make one Request for a user-specified timeslice of data.
1) Subscribe: 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.
2) 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.
3) 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.
More information about the Kepler-dev