W3C home > Mailing lists > Public > public-forms@w3.org > February 2010

Re: XForms initialization use case in response to ACTION-606

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Wed, 10 Feb 2010 11:26:10 -0800
Message-ID: <e81b48eb1002101126j49d35f27mc69e8d1dd52360d3@mail.gmail.com>
To: public-forms@w3.org
Leigh,

<xxf:join-submissions/> as used here waits for the completion of any
pending submission, no matter when they were started. It's quite easy
to implement, at least in Java.

I am not sure how the concept of starting point would work. But
couldn't a filter to specify which submission must be checked work,
e.g.:

<xxf:join-submissions submissions="load-i18n load-foobar"/>

-Erik

On Wed, Feb 10, 2010 at 10:30 AM, Leigh L. Klotz, Jr.
<Leigh.Klotz@xerox.com> wrote:
> I like xxf:join-submissions, but I wonder if it might be necessary to
> specify the start point, instead of relying on the form load as the start
> point.  It may be more important do to this once we incorporate
> components, because it would allow for better isolation of components. I
> can also imagine that even with current XForms, it may be necessary to
> specify a join start point that begins at some later point in the
> lifecycle.
>
> It may be that we can also use the start-point concept to control the
> trigger/action/send+ relationship to trigger re-enablement, as the trigger
> could wait for all its initiated actions.
>
> Additionally, it may be possible to expand the start-point to something
> ath would help identify and operate on outstanding submission requests and
> disambiguate their results (especially in the case of multiple outstanding
> submissions from the same submission element).  While it is possible to
> incorporate unique request values in the GET parameters or the POST entity
> (and pass them back to the response), it may be that offering built-in
> tracking all the way from the send or submission all the way though to the
> xforms-submit-done or -error event context info would be fairly easy to
> implement (as it's nearly required for xxf:join-submissions anyway) and
> convenient for application authors.  With unique ids (or serial numbers)
> for outstanding submissions, we also would obtain the ability to query
> submissions for progress, and to cancel them.
>
> Leigh.
>
>
>
>
Received on Wednesday, 10 February 2010 19:27:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:53 UTC