- From: Mark Birbeck <mark.birbeck@x-port.net>
- Date: Fri, 22 Oct 2004 11:27:43 +0100
- To: "'Durnell, Carryl'" <Carryl.Durnell@logicacmg.com>, "'Klotz, Leigh'" <Leigh.Klotz@pahv.xerox.com>
- Cc: <www-forms@w3.org>
Leigh/Carryl, Leigh wrote: > You might consider using <trigger> and <switch> and <case> to select > display of the user interfaces for the various forms instead of using > submission to the server. That may work in some situations, but the general problem is that many protocols require a URL to be set at run-time. For example, with Atom, you can establish the first URL that gives you a list of articles (such as your blog entries), but then to edit or delete each item, you need to interact with a specific URL that is specified in the instance data. Another example is that salesforce.com asks you to log on, and then returns an end-point that is to be used in all further exchanges. I believe this type of use to be a fundamental requirement for XForms if it is to be able to do useful work with SOAP, Atom, WebDAV and other protocols, and as Roland said, this is something that we hope to add in the future. In the meantime, formsPlayer now supports the use of xf:extension within xf:submission to allow *all* aspects of submission to be set from instance data (headers, URLs, methods, and so on). This should allow people to experiment with various protocols, and hopefully, through this experimentation we can work out what exactly we need to define in the spec. The new features are available in version 1.1 of formsPlayer, and a sample that connects to Blogger.com using the Atom API is available on our home page. Regards, Mark Mark Birbeck CEO x-port.net Ltd. e: Mark.Birbeck@x-port.net t: +44 (0) 20 7689 9232 w: http://www.formsPlayer.com/ Download our XForms processor from http://www.formsPlayer.com/
Received on Friday, 22 October 2004 10:28:11 UTC