- From: Klotz, Leigh <Leigh.Klotz@xerox.com>
- Date: Thu, 7 Jun 2007 16:58:27 -0700
- To: "Nikunj Mehta" <nikunj.mehta@oracle.com>, "Elliotte Harold" <elharo@metalab.unc.edu>, <www-forms@w3.org>, "atom-protocol Protocol" <atom-protocol@imc.org>
XForms 1.1 will add the ability to both set headers and to inspect HTTP return codes (necessary for delete). I expressed my concerns about using HTTP headers in APP a long time ago, but the consensus was that the value of having identical XML data was so great that the out-of-band channel was necessary. It's a pity that now that the APP data isn't strictly identical that there's still one header requires, but c'est la vie, and XForms 1.1 will accommodate it. Leigh. -----Original Message----- From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Nikunj Mehta Sent: Thursday, June 07, 2007 4:51 PM To: Elliotte Harold; www-forms@w3.org; atom-protocol Protocol Subject: Re: XForms and APP clients Elliotte Harold wrote: > > Has anyone yet written or started work on an XForms client for APP? I > googled but didn't find anything. If the space is open I may take a > crack at it myself. > > I think XForms 1.1 would be required since XForms 1.0 does not support > PUT and DELETE. > To be precise, XForms 1.0 supports PUT but *not *DELETE. Also, I did not find a way to submit the Slug header for initial entry POST. Nikunj
Received on Thursday, 7 June 2007 23:59:27 UTC