- From: Sebastian Schnitzenbaumer <schnitz@mozquito.com>
- Date: Tue, 7 Aug 2001 11:51:02 +0200
- To: "Schulze, Matthias" <schulze@dresden-informatik.de>
- Cc: <www-forms@w3.org>
- Message-ID: <D0F1529EE943B3449F755CA1A40887461116AD@winserver.windomain.mozquito.com>
Matthias, thanks for asking. XForms does provide a general approach for manipulating XML! Depending on the implementation, it can happen on the server or on the client. XForms is indeed client-centric in the sense that the manipulation of the XML ideally happens on the client and not on the server (you want changes made by the user to manipulate the XML immediately without network delays to present possible validation errors instantaneously to the user). But a servlet that performs the actual DOM access on the server could well be part of a more server-centric XForms implementation, it just depends on the implementation. Is this a bit clearer for you now? Please don't hesitate to ask if something is still unclear. The members of the XForms WG including myself are here to explain. All the best, - Sebastian -----Original Message----- From: Schulze, Matthias Sent: Sat 04/08/2001 19:06 To: Sebastian Schnitzenbaumer Cc: www-forms@w3.org Subject: AW: XForms & XSLT (was: Re: NetScape/IE) > When the user changes the settings, the copy > of the originating XML-A document loaded into the > browser gets changed. When the user hits submit, > the updated XML-A document overwrites the > existing XML-A document on the hard drive. Sebastian, I don't see how this might be accomplished using XForms alone. Changing the originating XML requires additional serverside logic, for instance a servlet that performs the actual DOM access. Will XForms really provide a general approach for manipulating serverside XML? If not, how can you say that "XForms is the XML-F back from XML-P to XML-A"? regards, Matthias
Received on Thursday, 9 August 2001 07:59:14 UTC