RE: xforms processors

> From: Karandikar, Shailesh [mailto:Shailesh.Karandikar@dendrite.com]

> Server side validation and workflow can not be eliminated. 
> However, with a
> client side validation, round trips to the server could be minimized,

Yes precisely. The argument of whether to handle XForms on the client
or the server ignores an intention of XForms. The purpose is to define
a form's elements, validation rules, and their relationships once,
and the client and the server *both* are capable of handling all of this.
Thus if the user makes a mistake, the client takes first swing, and
the server picks up the slack.

As an example, it's been suggested that this maybe-pioneering
form script by Peter Paul-Koch:

http://www.xs4all.nl/~ppk/js/usableforms.html

suffers from exactly the ailments XForms can solve. Sure it
performs well and only passes the needed elements back, but
what if Javascript is turned off? XForms to the rescue.


-Chris "SoopahMan" Moschini
http://hiveminds.info/
http://soopahman.com/

(this is a public mailing list - ignore attachment)

-------------------------------------------------------------------------------------

The information contained in this message is proprietary of Amdocs,

protected from disclosure, and may be privileged.

The information is intended to be conveyed only to the designated recipient(s)

of the message. If the reader of this message is not the intended recipient,

you are hereby notified that any dissemination, use, distribution or copying of 

this communication is strictly prohibited and may be unlawful. 

If you have received this communication in error, please notify us immediately

by replying to the message and deleting it from your computer.

Thank you.

-------------------------------------------------------------------------------------