events req servicing v2, with background computation, mod

[lttv.git] / ltt / branches / poly / doc / developer / lttvwindow_events_delivery.txt

diff --git a/ltt/branches/poly/doc/developer/lttvwindow_events_delivery.txt b/ltt/branches/poly/doc/developer/lttvwindow_events_delivery.txt
index a3586c0accb76e13e517142dfd777348e1ee7284..578abe0e67013d6085a4b8ed141316a49472c492 100644 (file)
--- a/ltt/branches/poly/doc/developer/lttvwindow_events_delivery.txt
+++ b/ltt/branches/poly/doc/developer/lttvwindow_events_delivery.txt
@@ -198,6 +198,17 @@ the initial request. This is the expected result. For the background processings
 that call viewer's hooks, they will be removed.
 
 
+A New "Redraw" Button
+
+It will be used to redraw the viewers entirely. It is useful to restart the
+servicing after a "stop" action.
+
+A New "Continue" Button
+
+It will tell the viewers to send requests for damaged areas. It is useful to
+complete the servicing after a "stop" action.
+
+
 
 Implementation
 
@@ -423,7 +434,10 @@ occur often. The solution to it would be to save one state per priority.
 
 Weaknesses
 
-- None (nearly?) :)
+- There is a possibility that we must use seek if more than one interruption
+  occurs, i.e. low priority interrupted by addition of high priority, and then
+  high priority interrupted. The seek will be necessary for the low priority.
+  It could be a good idea to keep one saved_state per priority ?
 
 
 Strengths