- From: Klotz, Leigh <Leigh.Klotz@xerox.com>
- Date: Thu, 26 Apr 2007 11:24:24 -0700
- To: <mark.birbeck@x-port.net>, "www-forms" <www-forms@w3.org>
There are two differences. 1. In my proposal, the server side returned url-encoded or base64 encoded text, which bind/@calculate turned into a data: URI for xf:load/@ref to show. This is, admittedly, a bit of a hack. Inaki's proposal to use a URI that refers to the resource which is now stored back on the server is still a hack, but less likely to cause problems with user agents. 2. If the server returned the data directly as application/xhtml+xml, xf:submission/@replace='all' still can't accomplish the effect of xf:load/@show='new'. Leigh. -----Original Message----- From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Mark Birbeck Sent: Thursday, April 26, 2007 9:52 AM To: www-forms Subject: Re: loading instance as .XML page Hi Iņaki, > I will finally do it in a Leigh-like way, but submitting data to a servlet > instead of a cgi (and the servlet will save the post-xml as xml document in > the DB with the xslt processing instruction on it) and then a xforms:load > @new action (inside submission) will load the document using the path that > the servlet returned from submission. But isn't that just the same as doing: <xf:submission method="..." action="..." replace="all" /> This will replace your current document with the results from the server. I got the impression from your initial mail that there was some reason you couldn't do this. > Mark, how can I turn my use case into a feature request? I must send it to > this mailing list or there are another channel?. I think you could send it to this list to begin with, and get some discussion going. Regards, Mark -- Mark Birbeck, formsPlayer mark.birbeck@x-port.net | +44 (0) 20 7689 9232 http://www.formsPlayer.com | http://internet-apps.blogspot.com standards. innovation.
Received on Thursday, 26 April 2007 18:24:39 UTC