Issue 4776: Event history                                                                                                                                                                                           (dais-ftf)
Source: ABB Power Technologies, Power Automation & Substat (Mr. Lars-Ola Osterlund, lars-ola.g.osterlund@se.abb.com)
Nature: Uncategorized Issue
Severity: 
Summary: It is not clear from the specification how the history of events is managed, e.g. how the server store events and make them available for future access.
Resolution: see above
Revised Text: Refer to comments in [1]
·	LOO128, LOO129, LOO133, LOO134, LOO135, LOO136 in section 5.2.4.2
·	LOO155 and LOO159 in section 5.2.10.2

Actions taken:
December 14, 2001: received issue
October 23, 2002: closed issue
Discussion: 
The method refresh_with_history() is renamed to async_read_history() following the pattern from Data Access and the end_time in parameter is replaced by number of events to give the client control over number of returned events.
End of Annotations:=====
Event history

It is not clear from the specification how the history of events is
managed, e.g. how the server store events and make them available for
future access.