RE: AJAX vs. Xforms

Erik,

Yes, you are right. I was thinking in terms of a different model for
submission errors, which I recently proposed to the Working Group. (And of
course is not available now!)

The problem my proposal attempts to solve is related to Daniel's but comes
at it from the other side; in SOAP over HTTP, you can get a 500 code
indicating that there was an error, but you can still get valid XML to tell
you about the error. SO you might get "Customer already exists" when you try
to add a new customer. I would have thought that Daniel's server would
ideally be doing something like that (which I think he does mention as a way
to go).

However, with XForms as it stands, an error code not only causes
xforms-submit-error, but also discards the returned data (the assumption
being that there isn't any). To do SOAP properly we need to get that data.

The exact way to resolve that is not completely clear, and there are a
number of fine proposals on the table. But it is something that is under
discussions.

However, as you say, you can't do this now...sorry if I caused any
confusion!

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/ 

> -----Original Message-----
> From: www-forms-request@w3.org 
> [mailto:www-forms-request@w3.org] On Behalf Of Erik Bruchez
> Sent: 26 October 2005 11:00
> To: www-forms@w3.org
> Subject: Re: AJAX vs. Xforms
> 
> 
> Mark,
> 
> Daniel doesn't only want to tell whether there was a success 
> or a failure, but also to display a series of errors returned 
> by the server. 
> In that case, the event sent upon the completion of the 
> submission will always be xforms-submit-done, whether his 
> server-side code succeeds or fails, since in both cases a new 
> instance containg the status of the server-side operations 
> will be returned successfully. So he needs some type of 
> conditions, whether by using relevant or conditional events, 
> as I suggested.
> 
> -Erik
> 
> Mark Birbeck wrote:
> > Erik,
> > 
> > Daniel doesn't actually need the conditional events feature for this
> > particular use case--as you said yourself, you get one 
> event for success and
> > one for failure, so he could put the toggle actions into 
> the xforms-submit-*
> > handlers.
> > 
> > (Which is not to say that we don't need the conditional handlers.)
> > 
> > Regards,
> > 
> > Mark
> 
>

Received on Wednesday, 26 October 2005 13:29:57 UTC