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

XForms Client versus Server

From: Steve Brimley <steve.brimley@toplev.com>
Date: Tue, 22 Jul 2003 12:42:16 +0100
Message-ID: <206030A1B6DDD5118C6E0050FC01A6A7024756@TOPLEVEL_SERVER>
To: "'www-forms@w3.org'" <www-forms@w3.org>

This is sent is response to an exchange between Chris Moschini and Shailesh

I would have thought that any implementation that relies on round trips to a
server will not be XForms compliant unless the server is contacted every
time the value of a control is altered.  The reason is that the form is
required to behave as though it is directly linked to the underlying XML
document.  That means that, if more than one control is linked to a
particular element, changing one should immediately change the other.  The
same logic applies to calculations using XPath.

I can't see a way round this.  For example, if two controls are linked to a
single element, and the client can't deal with this, how should the server
interpret the contradictory data sent to it?

Steve Brimley

Toplevel Computing
Received on Tuesday, 22 July 2003 09:29:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:08 UTC