W3C home > Mailing lists > Public > www-forms@w3.org > November 2006

Submission and deferred update [Re: XForms - Submission on multiple instances?]

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Wed, 1 Nov 2006 10:10:51 +0000
Message-ID: <640dd5060611010210n59f6a050l755b542b9f9deb63@mail.gmail.com>
To: www-forms@w3.org

Hi John,

> To reiterate, Section 11.1, point 5, bullet 2.
> The instance replacement of submission is followed immediately by *rebuild*,
> recalculate, revalidate, *refresh*.

It's true that the Second Edition spec is a bit clearer on the intent,
and the part you refer to says this:

  Once the XML instance data has been replaced, the rebuild, recalculate,
  revalidate and refresh operations are performed on the model, without
  dispatching events to invoke those four operations. Submit processing
  then concludes after dispatching xforms-submit-done.

That's a little clearer than the first edition, which said this:

  [T]he response is parsed as XML and all of the internal instance data
  corresponding to the submitted instance is replaced with the result,
  using the same processing as remote instance data retrieved through
  src, and the xforms-model-construct event is dispatched to element
  model. Submit processing then concludes after dispatching
  xforms-submit-done.

> These are *not* deferrred update behaviors after some action (submission is not an
> action; send is an action, but all it does is *initiate* a submission).
> The rebuild, recalculate, revalidate, refresh are mandatory behaviors that occur *before*
> xforms-submit-done is dispatched.

Although submission is not an action, it can only 'do its thing'
within an action handler. And since, according to 10.1.1, this:

  <xf:action ...>
    <xf:send ... />
  </xf:action>

will have deferred update behaviour, it seems that this in effect
'overrides' the update behaviour in 'send'.

Now, you could say that this is just an ambiguity, and that it's not
really clear which should take priority--the deferred update, or
performing RRRR immediately--so I took a look at your latest XForms
1.1 draft, to see if you'd made it more explicit , and I discovered
that it now says this:

  Once the XML instance data has been successfully  replaced, the rebuild,
  recalculate, revalidate and refresh operations are performed on the model,
  without dispatching events to invoke those four operations. This sequence of
  operations is associated with special deferred update behavior. Submission
  processing then concludes after dispatching xforms-submit-done with
  appropriate context information.

On other words, the additional second sentence seems to make it even
clearer that the RRRR is subject to deferred update!

I thought it worth flagging up.

Regards,

Mark

-- 
Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
http://www.formsPlayer.com/
Received on Wednesday, 1 November 2006 10:11:03 GMT

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