W3C home > Mailing lists > Public > www-forms@w3.org > July 2009

RE: dispatch with @delay question

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Fri, 10 Jul 2009 10:11:18 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF4082E192D@USA7061MS01.na.xerox.net>
To: "Aaron Reed" <aaronr@us.ibm.com>, <www-forms@w3.org>
Aaron,
We discussed this issue [1] at our teleconference and the conclusion was that the XForms Recommendation is correct as written, and that your concerns are appropriate for the Recommendation to leave to the implementation.  In other words, we didn't define it but it's reasonable for an implementor to assume that no further events happen after model-destruct. It's safe to assume that after model-destruct event dispatch is finished, no further delayed events occur.

If this doesn't answer your concern, please let us know.

[1] http://lists.w3.org/Archives/Public/public-forms/2009Jun/att-0063/2009-06-17.html#topic5 

Leigh.

-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Aaron Reed
Sent: Thursday, June 04, 2009 2:21 PM
To: www-forms@w3.org
Subject: dispatch with @delay question

Hi,

I didn't see this in the spec, but perhaps I missed it.

I see in the spec rules like removing the event from the delay queue before dispatching and if the target is deleted then the event should be removed from the delay queue.  But I don't see anything in the spec that mentions when all of the events in the delay queue should be destroyed. 
  Should that happen as part of the xforms-model-destruct default handling?  This seems like the type of thing that should be defined in the spec if it isn't already.

Thanks,
--Aaron
Received on Friday, 10 July 2009 17:14:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:16 GMT