how to handle notification delays in SMIL implementation

Hi,

I have a question regarding handling of notification
delays in a SMIL implementation. 

Suppose I have a SMIL implementation that sends begin
& end notifications to the application, and receives
notifications of events (such as mouse clicks) and
times from the calling application (time is fed to the
SMIL by the application). What should happen if
notifications of times and/or events between the SMIL
and the application are delayed? 

For example, what if the SMIL engine detects that a
movie should have begun at time=5s, but by the time it
detects this it is already time=10s (due to delays in
receiving events and time notices), and perhaps in
addition, something else should have happened at
time=7s. 

Do the events get queued up and fired up immediately
in order? Or does time instead get dilated (or
omitted) so that even though in reality 10s have
elapsed, we pretend that we have only reached time=5s,
and quietly throw away the extra 5s as if they hadn’t
elapsed, so that everything else could proceed as
normal.

Is there a commonly accepted way to handle this and
related scenarios? 

Thanks in advance,

Annie





__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Received on Tuesday, 23 September 2003 18:43:23 UTC