← Prev in month ← Prev in thread
Next in thread → Next in month →

Eliminating StopHistorian/StoppedHistorian - urgent for Thursday mid-day

From
William Cox
Date
2011-10-26T19:34:00+00:00
ID
Thread
Eliminating StopHistorian/StoppedHistorian - urgent for Thursday mid-day
See  http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-598  and
comment ASAP.
Detailed proposal from the Jira item:
Eliminate StopHistorian and StoppedHistorian.
Add to the CancelHistorian payload:
 sendFinalReport: boolean [1..1] - if absent or false, stop the
historian and market buffered data for deletion. If true send a
final report using the reportID
 reportID [0..1] MUST be present if sendFinalReport is true.
Indicates what report to send the next/final of to take care of
all flushed data. Normal rules apply for when the buffered data is
marked for deletion or implicitly marked.
I think that a reportID must be present if a final report is needed,
because the Historian records the data and does not send the report.
This is a bit not to my liking because it couples a report action
with historian actions which are logically and architecturally
separate. But only a bit...
I'd prefer
    CancelHistorian has deleteHistory:boolean that hints that the
History to date be deleted (TRUE) or not be deleted (FALSE)  -
marked for deletion
Then you send report requests as usual until you've consumed the
data recorded.
Comments?

--
William Cox
Email:  
Web:  http://www.CoxSoftwareArchitects.com
+1 862 485 3696 mobile
+1 908 277 3460 fax
← Prev in month ← Prev in thread
Next in thread → Next in month →